Ambiguous tools
Agents may pick the wrong operation when names and descriptions are too vague.
TimeProofs AgentReady scans OpenAPI specs and MCP tool definitions locally in the browser. It returns a score, risk findings, a human report, agentready.json, and static scenario simulation output.
Human documentation often leaves too much unsaid for autonomous tools: when to use an endpoint, when not to use it, which values are allowed, what requires confirmation, and how to recover from errors.
Agents may pick the wrong operation when names and descriptions are too vague.
Money, deletes, emails, exports, and publishing flows need limits and confirmation rules.
Generic errors leave agents guessing instead of correcting parameters or stopping safely.
Start with the artifact you already have. Get a readiness contract that humans can read and future automation can consume.
Choose an OpenAPI JSON/YAML file or an MCP tools JSON file. The current V1 scanner runs in the browser.
Read the AgentReady Score, severity counts, tool findings, recommended fixes, and printable report.
Use agentready.json with static scenarios to check risky task patterns before live execution.
OpenAPI or MCP tools JSON -> AgentReady analysis -> AgentReady Score -> risk findings -> recommended fixes -> human report -> agentready.json -> static scenario simulation -> agentready-simulation.json
Useful before you publish an MCP server, expose internal APIs to an AI agent, prepare agent-facing documentation, or review a tool surface before production.
TimeProofs AgentReady is not a runtime firewall and does not guarantee that an AI agent will never fail. It identifies structural risks that may cause AI agents to misuse APIs, tools, or MCP servers.