Machine-readable name for the proposed tool.
Natural language description of the tool's purpose and behaviour.
JSON Schema defining the tool's input arguments.
Optional outputJSON Schema defining the tool's expected output shape (optional).
The tool's source code (for sandbox mode) or serialized composition spec (for compose mode). Included in the LLM prompt for security auditing.
Whether the tool was built by composing existing tools ('compose') or
by running arbitrary code in a sandbox ('sandbox').
Optional allowlistSandbox API allowlist — the set of APIs the tool's code is permitted to
invoke. Only relevant for 'sandbox' mode tools. Used by the safety
auditor to verify that the code does not exceed its declared API surface.
Results of test runs executed against the candidate tool before review. Each entry contains the input, output, success flag, and optional error. The judge uses these to assess correctness and determinism.
Optional error?: string
A candidate tool submitted for creation review by the EmergentJudge.
Contains all the information the judge needs to evaluate safety, correctness, determinism, and bounded execution: the tool's identity and schemas, its source code or composition spec, the sandbox API allowlist, and the results of any test runs.