Skip to main content
Glama

Usc Titles

usc_titles
Read-onlyIdempotent

List the 54 titles of the United States Code with their subject names, title 18 is Crimes and Criminal Procedure, title 26 is the Internal Revenue Code, and so on. Keyless. Use when you know the subject area but not which title governs it, before calling usc_section.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, openWorld, and non-destructive, so safety is covered. The description adds context the annotations do not: 'Keyless' tells the agent no credential set-up is needed, and the phrasing makes clear the output is a static reference list of 54 entries rather than a paged or filtered query.

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?

Two sentences, front-loaded with the resource and its return contents before the usage note. The title 18 / title 26 examples earn their space as concrete anchors, though 'and so on' is filler that could be dropped without loss.

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?

For a no-parameter, read-only reference listing with no output schema, the description supplies everything needed to call it correctly: it names the resource, the count, the shape of each entry (title number + subject name), and where it fits relative to usc_section. Nothing material is missing.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to carry; the schema coverage of 100% with an empty properties object is consistent with a pure static listing. Baseline 4 applies, with no wording implying hidden inputs like filtering or pagination.

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?

A specific verb plus resource: 'List the 54 titles of the United States Code with their subject names', immediately grounded with concrete examples (title 18 = Crimes, title 26 = Internal Revenue Code). An agent knows exactly what this returns and how it differs from a single-section lookup like usc_section.

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 triggering condition — 'use when you know the subject area but not which title governs it' — and sequences it before usc_section, which is genuinely actionable routing guidance. It stops short of stating when not to use it (e.g., when the title number is already known and a section lookup is the direct path).

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.