Skip to main content
Glama

Usc Search

usc_search
Read-onlyIdempotent

Search the United States Code by subject to find which statutes are relevant, "wire fraud", "endangered species take". Returns matching section headings and their titles; call usc_section for the text. Needs a data.gov API key, which Pipeworx fronts; pass _apiKey to use your own. For a citation you already have, usc_section is keyless and more direct.

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": {
      "limit": 5,
      "query": "wire fraud"
    },
    "name": "usc_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results (1-50, default 10).
queryYesSubject matter, e.g. "wire fraud" or "clean water discharge permit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and open-world behavior, so the bar is lower; the description earns credit by disclosing the return shape (headings and titles, no full text) and the auth requirement (data.gov API key fronted by Pipeworx, with _apiKey override). It does not discuss rate limits, result ordering, or empty-result behavior, which keeps it short of 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?

Four tight sentences in a deliberate order: purpose with examples, return shape, auth, then the alternative. Nothing is repeated and the disambiguating advice is placed last where it reads as a decision rule.

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 no output schema, the description still explains what is returned and that full text requires a second call, and it covers the auth model and the key sibling tradeoff. An agent has everything needed to call it correctly and to chain it.

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 both parameters are documented, but the description adds the crucial semantic framing that query is subject matter rather than a citation. It also surfaces the _apiKey override, which does not appear in the input schema at all — genuine value beyond the structured fields.

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 gives a specific verb and resource ("Search the United States Code by subject") plus two concrete example queries ("wire fraud", "endangered species take") that pin down the intended granularity. It also states what comes back (matching section headings and titles), so an agent knows this is a discovery tool rather than a text-fetch tool.

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 provides explicit routing: use this when you know a subject, and use usc_section when you already have a citation, with a reason ("keyless and more direct"). The follow-up step ("call usc_section for the text") completes the workflow 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.