Generate MCP servers from OpenAPI specifications
This is a code generator, not an MCP server itself. The single tool 'get_api_info' in generator.py is severely underdeveloped. No input schema visible (empty {}), minimal description ('Get API information'), and no documented output structure. The generator templates reference MCP tool definitions that will be created dynamically, but the generator itself is not production-ready as an MCP server. The tool does not follow naming conventions (should be 'describe_api' or 'fetch_api_metadata'), has trivial documentation, and provides no guidance on usage, parameters, or return format.
Create a note and place it into the note tree
deletes a single note based on the noteId supplied
Exports ZIP file export of a given note subtree. To export whole document, use "root" for noteId
Returns a note identified by its ID
Returns note content identified by its ID
patch a note identified by the noteId with changes in the body
Updates note content identified by its ID
Tool 'get_api_info' has empty input schema ({}). No parameters defined or documented.
Tool description is trivial ('Get API information'). Does not explain WHAT the tool does, WHEN to use it, WHAT it returns, or any prerequisites.
No output schema documented. LLMs cannot infer what fields to expect or plan downstream calls.
Tool name 'get_api_info' is generic and ambiguous. Does not follow verb_noun pattern clearly, 'get' is correct but 'api_info' is vague. Should be 'describe_openapi_spec' or 'fetch_api_metadata'.
No error handling guidance. If the API is unreachable or the OpenAPI spec is malformed, the tool provides no recovery instructions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 12 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 14 | - | v1 |
Search notes