knowledge-commons

Search HTTP RFC clauses (exact quotes)

search_clauses

Read-onlyIdempotent

Search HTTP requirements, caching rules, headers and status-code semantics in RFCs 9110–9114 by concept, words, RFC section or stable id. Each result carries quote_official: the exact official RFC text, plus conditions, exceptions, related clauses and errata. When to use: Use when you must answer what an HTTP standard requires (MUST/SHOULD/MAY) and cite it. Cite quote_official to the letter, including spaces and newlines; null means no verified text, so do not invent one. Use get_clause for more context on one result. Notes: No account or token needed. At most 5 groups; ranked results and companion groups each have a 48,000-character text budget; truncation is explicit. Example arguments: {"query":"must-revalidate when origin is unreachable","limit":5}

Input Schema

Name	Required	Description
`rfc`	No	Only this RFC, e.g. 9111 or 'RFC 9111'.
`limit`	No	Positive ranked-result count (default 5, capped at 50); numeric strings are accepted.
`query`	Yes	HTTP concept, words, 'RFC 9111 5.2.2.2' or a stable clause id (English or Italian).
`expand`	No	Add companion clauses from the same section and linked references (default true).
`keyword`	No	Only clauses with this BCP 14 keyword (case-insensitive, e.g. MUST or must).
`addressee`	No	Only clauses addressed to this party, e.g. 'cache', 'origin server', 'client'.
`expansion_limit`	No	Maximum companion clauses, 1–48 (default 24).

Output Schema

Name	Required	Description	Default
`limit`	No
`total`	No
`corpus`	No
`errore`	No
`expand`	No
`groups`	No
`ranking`	No
`results`	No
`contratto`	No
`messaggio`	No
`expansion_limit`	No
`results_truncated`	No
`status_originario`	No
`expansion_truncated`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed13 schema fields changedOct 25, 2026

changedInput schema / properties / keyword / description

Previous value: -"Only clauses with this BCP 14 keyword."New value: +"Only clauses with this BCP 14 keyword (case-insensitive, e.g. MUST or must)."

removedInput schema / properties / keyword / enum

Removed value: -[
-  "MUST",
-  "MUST NOT",
-  "REQUIRED",
-  "SHALL",
-  "SHALL NOT",
-  "SHOULD",
-  "SHOULD NOT",
-  "RECOMMENDED",
-  "NOT RECOMMENDED",
-  "MAY",
-  "OPTIONAL"
-]

addedInput schema / properties / limit / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "pattern": "^\\d+$",
+    "type": "string"
+  }
+]

removedInput schema / properties / limit / default
```
Removed value: -5
```

changedInput schema / properties / limit / description

Previous value: -"Ranked results, 1–50 (default 5)."New value: +"Positive ranked-result count (default 5, capped at 50); numeric strings are accepted."

removedInput schema / properties / limit / maximum
```
Removed value: -50
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```
removedInput schema / properties / limit / type
```
Removed value: -"integer"
```

addedInput schema / properties / rfc / anyOf

Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "pattern": "^(?:RFC\\s*)?\\d+$",
+    "type": "string"
+  }
+]

changedInput schema / properties / rfc / description

Previous value: -"Only this RFC number, e.g. 9111."New value: +"Only this RFC, e.g. 9111 or 'RFC 9111'."

removedInput schema / properties / rfc / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / rfc / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / rfc / type
```
Removed value: -"integer"
```

Changed7 schema fields changedOct 21, 2026

addedInput schema / properties / addressee / description

Added value: +"Only clauses addressed to this party, e.g. 'cache', 'origin server', 'client'."

addedInput schema / properties / expand / description

Added value: +"Add companion clauses from the same section and linked references (default true)."

addedInput schema / properties / expansion_limit / description

Added value: +"Maximum companion clauses, 1–48 (default 24)."

addedInput schema / properties / keyword / description

Added value: +"Only clauses with this BCP 14 keyword."

addedInput schema / properties / limit / description

Added value: +"Ranked results, 1–50 (default 5)."

addedInput schema / properties / query / description

Added value: +"HTTP concept, words, 'RFC 9111 5.2.2.2' or a stable clause id (English or Italian)."

addedInput schema / properties / rfc / description

Added value: +"Only this RFC number, e.g. 9111."

AddedOct 17, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses that results carry exact quote_official text, that null means no verified text and must not be invented, that no account or token is needed, and that result budgets/truncation are explicit. These are operationally relevant traits an agent would not get from the annotations alone.

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?

The description is front-loaded with purpose, then structured into when-to-use and notes, followed by a compact example. Every sentence contributes either routing guidance, citation safety, or operational constraints.

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

Completeness5/5

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

With an output schema present, the description need not explain return fields, and it instead covers the high-risk parts: exact quote citation, null handling, companion expansion budgets and the sibling get_clause route. Together with 100% schema coverage and clear annotations, the definition is complete for correct invocation.

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?

Schema description coverage is 100%, so the schema already documents all seven parameters, including rfc, query, limit, expand and expansion_limit. The description adds only an example argument pair and high-level query modes, so it does not meaningfully exceed the schema's parameter documentation.

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?

The description states a precise verb and resource: search HTTP requirements, caching rules, headers and status-code semantics in RFCs 9110–9114 by concept, words, section or id. It also distinguishes the result type via quote_official and explicitly names get_clause as the deeper-context 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?

It gives an explicit when-to-use rule: answer what an HTTP standard requires (MUST/SHOULD/MAY) and cite it. It also states that get_clause should be used for more context on one result, so the agent has a clear alternative.

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

All knowledge-commons tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?