RFC MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_rfcB | Fetch an RFC document by its number |
| search_rfcsC | Search for RFCs by keyword |
| get_rfc_sectionC | Get a specific section from an RFC |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_rfc retrieves a full document, get_rfc_section extracts a specific part, and search_rfcs finds documents by keyword. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case (get_rfc, get_rfc_section, search_rfcs). The naming is predictable and readable, with no deviations or mixed conventions.
With 3 tools, the server is well-scoped for its purpose of accessing RFC documents. Each tool earns its place by covering distinct aspects (fetching, sectioning, searching), and the count is appropriate without being too thin or heavy.
The tool surface covers core operations for RFC access: retrieving full documents, sections, and searching. A minor gap exists in lifecycle coverage, such as listing all RFCs or filtering by metadata, but agents can work around this with the provided tools.