Identity Forge MCP has 13 tools with schemas and descriptions visible in source code. However, numerous critical gaps prevent a higher score. Tool naming follows verb-first conventions (check_, list_, get_, create_, generate_, apply_, export_, share_, assess_), which is good. Descriptions exist but are quite brief (averaging ~60 chars), below the 194-char baseline for production tools. Parameter descriptions are present but minimal. Critically, NO tools have documented output schemas, responses are completely undocumented, forcing LLMs to guess what fields will be returned and breaking tool chaining. Error handling guidance is absent. Schemas are basic JSON Schema with types but lack constraints (enums, ranges, patterns). STDIO transport caps protocol readiness at 50 regardless of definition quality.

• Add output schemas to every tool. For list_themes, document: { type: 'object', properties: { themes: { type: 'array', items: { type: 'object', properties: { id: { type: 'string' }, name: { type: 'string' }, ... } } }, total: { type: 'integer' } } }. For whoami, document the returned user object fields (id, email, name, tier).
• Expand tool descriptions to 120 - 200 chars. Add context: WHEN to call, what it returns, and what to do next. E.g., 'Get the current authenticated user account information, including email and tier. Call this first to verify API key and retrieve user_id for subsequent operations.' instead of the current one-liner.
• Convert format and constraint descriptions into JSON Schema enums and patterns. E.g., for get_tokens, add 'enum: ["dtcg", "css", "tailwind-v3", "tailwind-v4", "shadcn-registry", "json"]' in the format parameter schema.
• Add explicit pagination to list_themes and list_name_candidates: 'limit' (1 - 100, default 20) and 'offset' (default 0) parameters. Document: 'Returns up to limit items and a total count. Use offset to fetch subsequent pages.' Implement cap enforcement in the handler.
• Add error handling notes to all WRITE tools. E.g., apply_theme: 'If the directory does not exist, returns 404 with available directories. If format is invalid, returns 400 with valid options. Retryable: network errors (5xx). Non-retryable: invalid format, missing directory.'
• Document tool chaining in descriptions. E.g., create_naming_project description: 'Creates a naming project. Returns project_id. Next: call generate_names(project_id) to create candidates, then list_name_candidates(project_id) to retrieve them.'