MCP server for editing RFC documents using rfc-editor library
18 tools with explicit schemas and descriptions, but critical gaps undermine quality. All tools have descriptions (10-50 chars, mostly generic), and input schemas are present but severely underdeveloped. Parameter descriptions are minimal or absent (e.g., 'RFCDocument' with no explanation of structure). No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint/destructiveHint). Naming is verb-forward (get_, set_, add_, update_) but many tools are granular getters (get_title, get_abstract, get_copyright) that could be consolidated. The 'document' parameter appears in 14 tools but is never explained, LLMs cannot infer it's a complex object. No pagination, no result limits, no chaining IDs. Security: no secrets exposed, but no permission gates or audit trails. Composition: heavy reliance on passing RFCDocument objects between tools creates tight coupling and requires LLMs to manage state manually.
Add a new section to an RFC document
Create a new empty RFC document
Download an RFC by number from rfc-editor and parse it
Get the abstract of an RFC document
Get the acknowledgements of an RFC document
Get the authors address section of an RFC document
Get the contributors of an RFC document
Parameter 'document' (type: object) appears in 14 tools with only generic description 'RFCDocument'. No schema details, no explanation of required fields, no guidance on how to construct or pass it. LLMs cannot infer structure.
14 getter tools (get_title, get_abstract, get_copyright, etc.) each do one trivial thing. No consolidation into a single 'get_rfc_metadata' or 'get_rfc_section' tool. Forces LLM to make many sequential calls for what could be one batch operation.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Get the copyright notice of an RFC document
Get the current active RFC document from session context
Get a section by its title
Get the status of this memo section
Get the title of an RFC document
Get the table of contents
Load an RFC TXT file and parse its sections
Save an RFC document to a TXT file
Set the abstract of an RFC document
Set the title of an RFC document
Update an existing section in an RFC document
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields. E.g., load_rfc returns an RFCDocument but no schema shows what fields it contains.
No error handling guidance. Tools like download_rfc and load_rfc can fail (network, file not found, parse error) but no recovery hints provided. LLMs receive raw errors with no actionable next steps.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot distinguish safe reads from destructive writes. E.g., save_rfc and update_section modify state but carry no warning.