AI App Readiness Checker

Use when checking supplied AI App identity fields such as name, slug, repository, Worker name, wrangler name, website URL, MCP URL, and support email. It returns missing fields, consistency findings, and fixed-ruleset readiness status. It does not access URLs, call GitHub or Cloudflare, deploy, rename, modify resources, or guarantee final platform approval.

check_app_identity

Use when checking supplied MCP tool definitions for frozen names, descriptions, inputSchema, outputSchema, annotations, structured output fields, error contract, and read-only boundaries. It accepts user-provided tool definitions and returns contract findings. It does not execute tools, rewrite schemas, call external APIs, access URLs, or guarantee approval.

check_mcp_tool_contract

Use when checking supplied submission materials such as app display assets, developer/company information, privacy policy URL, MCP and tool information, test prompts and expected responses, localization declaration, review shell page statuses, demo information, prompts, release notes, domain verification, and challenge route status. It returns missing material findings under the fixed ruleset. It does not create, upload, verify, submit, publish, access URLs, or guarantee approval.

check_submission_materials

Use when identity, MCP tool contract, and submission material check results are already supplied and a final READY or NEED_FIX readiness verdict is needed. It returns completed checks, missing checks, blockers, findings, and fixed-ruleset verdict. It does not perform underlying checks, invent evidence, submit or publish the app, access external systems, or guarantee approval.

generate_submission_verdict