Skip to main content
Glama

Usc Section

usc_section
Read-onlyIdempotent

Get the FULL TEXT of a section of the United States Code, federal statutes, by citation. "18 U.S.C. 1343" is title 18, section 1343. Returns the statutory text, its title and chapter, and the edition it came from. Keyless. Use for "what does the wire fraud statute say", "what is the text of 42 USC 1983", or to check what a statute a case relies on actually provides.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "18",
      "section": "1343"
    },
    "name": "usc_section"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesUS Code title number, 1-54. E.g. "18" for crimes, "26" for tax, "42" for public health and welfare.
sectionYesSection number as cited, e.g. "1343" or "1983". Subsections like "1343(a)" are not separate documents, pass the section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / section / description
      Previous value: -"Section number as cited, e.g. \"1343\" or \"1983\". Subsections like \"1343(a)\" are not separate documents — pass the section."New value: +"Section number as cited, e.g. \"1343\" or \"1983\". Subsections like \"1343(a)\" are not separate documents, pass the section."
  2. First observed

TDQS

A4.4/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, open-world), yet the description adds genuinely new facts: "Keyless" (no auth required) and specifically what comes back — statutory text, title, chapter, and source edition. It doesn't cover miss behavior (unknown title/section) or size of returned text, which keeps it from 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?

Front-loads the core capability in the first clause, then adds format, return contents, auth note, and use cases in tight sequence with no filler. Example queries are quoted inline as routing cues rather than padding.

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 two-parameter read tool with full schema coverage and no output schema, the description supplies return-value expectations and the citation convention, which is enough to call it correctly. The one missing piece is what happens when a title/section doesn't exist or is invalid, which matters for a citation-driven lookup.

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%, so the baseline is 3, but the description adds real semantic value by teaching the citation-to-parameter mapping (title number and section number inside a legal citation). The schema itself also clarifies that subsection suffixes like "1343(a)" should be folded into the section rather than treated as separate documents.

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?

States a specific verb and resource ("Get the FULL TEXT of a section of the United States Code") and pins the access mode to citation lookup, which implicitly separates it from search-style siblings like usc_search and usc_titles. The citation-format example ("18 U.S.C. 1343" = title 18, section 1343) removes any ambiguity about what a 'section' means here.

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?

Provides concrete triggering scenarios ("what does the wire fraud statute say", "what is the text of 42 USC 1983", checking a statute a case relies on), so an agent knows when this is the right tool. It stops short of naming a sibling and saying when NOT to use it (e.g., keyword/hypothesis search belongs in usc_search).

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.