ADVANCED CONSOLE · AGENT DEVELOPER
Inspect the context before calling the model
Paste a catalog in JSON. The console checks whether descriptors, schemas, risk, and evidence are suitable for the discovery and execution pipeline.
01 · Contract
Name, title, description, and uniqueness.
02 · Schema
Types, properties, required fields, and limits.
03 · Operations
Cancellation, risk, confirmation, and output.
LOCAL INPUT
JSON catalog
Use an array of descriptors. Since functions don’t exist in JSON, declare executeBehavior and operational evidence separately.
Nothing is sent to a server, registered in document.modelContext, or executed.
0out of 100
No diagnosis
Catalog quality
Load the example or paste your JSON to get started.
0
Passed
0
Considerations
0
Failures
Findings will appear here, prioritized by impact.
What this scanner does not prove
- • native browser support;
- • backend authorization;
- • security of execute code;
- • real quality without execution tests.
Next training labs
- • tool selector with a dataset;
- • executor with a policy gate;
- • evaluation of complete conversations.