Manifest schema
—
name, description, parameters
Define / validate / discover
Make the contract
earn its line.
A one-line tool is only useful when its inputs are explicit. Compile the schema, test representative args, and keep runtime claims outside the proof.
Waiting for a contract
Load the sample to compile a manifest and validate its args.
Sample args
—
compiled parameter schema
Parameters
—
properties in schema
Required
—
fields required at call time
Discoverable command preview
waiting for a valid manifest
The completed audit will distinguish schema shape from argument validity.
Interpretation boundary
Schema validity is a contract checkpoint, not proof that a tool executes, has safe permissions, or matches any named extension's runtime API.
Schema validity is a contract checkpoint, not proof that a tool executes, has safe permissions, or matches any named extension's runtime API.
Shape before execution
A tool name and description make discovery readable. A JSON Schema makes its input boundary executable and testable.
Pass is not permission
Even valid args can trigger unsafe effects. Authorization, side-effect review, and runtime integration remain separate gates.