Skip to main content
Glama

List SAT-published contributor lists an RFC appears in

rfc_sat_lists
Read-only

List SAT-published contributor lists an RFC appears in. Asks the government registry for real and is billed to the connected account: see get_account for what it costs you. Only send identifiers the user gave you. Details: read_doc "rfc/endpoints/sat-lists".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rfc": "<rfc>"
    },
    "name": "rfc_sat_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfcYesThe RFC number to validate (12 or 13 characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new behavior: the data comes from a real government registry and the call is billed to the connected account. The privacy constraint on identifiers is also disclosed. It doesn't quantify cost or latency, which keeps it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, each carrying a distinct fact: what is listed, that it costs money and where to check that, and the identifier constraint, followed by a pointer to read_doc. Nothing is repeated and the purpose is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the description covers source, cost, and input constraint, and it points to read_doc for the response shape. It is nearly complete; only the returned structure is left entirely to the external doc.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema description coverage, so the schema already documents the RFC number. The description only adds a sourcing rule for the identifier ('only send identifiers the user gave you') and no format or validation detail beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it lists SAT-published contributor lists that an RFC appears in, which is more precise than a generic lookup. It doesn't contrast itself with siblings like rfc_profile or rfc_validate, but the resource is distinctive enough that an agent can tell what it returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear operative constraint ('Only send identifiers the user gave you') and routes the agent to get_account for cost and read_doc for endpoint details. It stops short of saying when to prefer this over the other rfc_* tools, so it is clear context rather than full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources