The gaphor-mcp tool lacks visible input schema, parameter descriptions, and output schema documentation in the provided source. Only a pyproject.toml entry point is shown; no actual tool registration code, parameter definitions, or handler implementation are visible. The description 'MCP server to generate, inspect, render and export Gaphor sequence diagrams' is present but generic (67 chars). Without access to the actual tool handler code (gaphor_mcp module), parameter schemas, and return types, this cannot be scored above the inference cap of 50. The single tool appears to combine multiple responsibilities (generate, inspect, render, export) into one, violating single-responsibility principle.

• Provide the actual gaphor_mcp module source code showing tool registration, parameter schemas, and return types.
• Rename tool to action-verb form: 'generate_sequence_diagram', 'render_diagram', 'export_diagram', 'inspect_diagram' (separate tools).
• Add explicit JSON Schema input definitions with type, description, and enum/pattern constraints for each parameter.
• Document output schema with field names, types, and descriptions so LLMs know what to expect.
• Expand tool descriptions to 100-150 chars explaining: what it does, when to call it, what it returns, and any prerequisites (e.g., 'Requires a valid Gaphor diagram file path').