list_rfcsList the AIO public RFCs — the public comment periods in which a contested standards-pack or methodology decision is put out for comment before it is treated as settled. Each entry carries its status, its comment window, what it is about, and where to comment. Review windows follow the AIO Public RFC Process v1.0 (Draft ≥ 14 days, Candidate ≥ 30 days). CC BY 4.0.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safe/idempotent/read-only profile, so the description's added value is real: it enumerates what each entry carries (status, comment window, subject, where to comment) and states the process deadlines of ≥14 days for Draft and ≥30 days for Candidate. It omits ordering, pagination, and whether the list is exhaustive, which are the remaining operational unknowns for this exchange.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The purpose clause is front-loaded and the resource definition follows immediately; the entry-fields sentence earns its place by describing output. The process-version and 'CC BY 4.0' license tail is metadata of marginal selection value and slightly dilutes an otherwise tight definition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no parameters and no output schema, the description carries the return shape itself and does so adequately (status, window, subject, comment location), plus the window-length rules. It leaves the interaction loop underspecified — nothing tells the agent that commenting happens via `submit_rfc_comment` for an item obtained from this list.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so per the baseline there is nothing for the description to disambiguate. The schema is empty and no parameter explanation is required or offered, and none is missing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and a precisely characterized resource (AIO public RFCs, defined as public comment periods for contested standards-pack or methodology decisions). The definition of what an RFC is here meaningfully separates it from sibling resources like standards packs or papers. It stops short of naming `get_rfc` as the single-record counterpart, so differentiation is inferred rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Browsing intent is implied by 'List' and by the promise that each entry carries status and comment window, but there is no explicit when-to-use or when-not guidance. With both `get_rfc` and `submit_rfc_comment` as siblings, the description should say to use this to find an RFC and the others to read or comment on one; that routing is absent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.