Skip to main content
Glama

Read one HTTP RFC clause

get_clause
Read-onlyIdempotent

Return one clause card by stable id: full official paragraph (quote_official), conditions, exceptions, definitions, linked sentences, related ids, RFC status and errata. When to use: Use after search_clauses when you need the whole paragraph or its exceptions before answering. Never cite presentation_text as official wording. Then cite_source gives the citation and a stable public page for the clause. Notes: No account or token needed. Example arguments: {"id":"rfc9110-s13.1.3-c1"}

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": {
      "id": "<id>"
    },
    "name": "get_clause"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesStable clause id from search_clauses, format rfcNNNN-sSECTION-cN.

Output Schema

NameRequiredDescriptionDefault
clauseNo
erroreNo
contrattoNo
messaggioNo
status_originarioNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / id / description
      Added value: +"Stable clause id from search_clauses, format rfcNNNN-sSECTION-cN."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's real contribution is the field-level warning 'Never cite presentation_text as official wording' plus 'No account or token needed'. That caveat about which returned field is authoritative is genuinely valuable context an agent would otherwise miss; only return-shape details are left to the output schema.

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

Conciseness4/5

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

Labeled sections (When to use, Notes, Example arguments) make it scannable and the exclusions are front-loaded. Slightly dense wording in the first sentence's inventory of return fields is the only cost, but each item conveys what the card contains.

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 single-parameter read tool with an output schema and full annotation coverage, this covers what an agent needs: how to obtain the id, what the card gives back, which field is citable, and what to call next. Nothing essential is absent.

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

Parameters4/5

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

Schema coverage is 100% with a regex pattern and a description already tying the id to search_clauses, so the baseline would be 3. The concrete example argument {"id":"rfc9110-s13.1.3-c1"} goes slightly beyond the pattern by showing a real-world instance, though it adds no new semantic constraints.

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

Purpose5/5

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

Opens with a specific verb and resource: 'Return one clause card by stable id', then enumerates the payload (quote_official, conditions, exceptions, definitions, linked sentences, related ids, RFC status, errata). This clearly separates it from search_clauses, the bulk-retrieval sibling.

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

Usage Guidelines5/5

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

'Use after search_clauses when you need the whole paragraph or its exceptions before answering' gives an explicit trigger condition and names the predecessor tool. It also positions cite_source as the next step, so the agent sees the full call sequence, not just an isolated hint.

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