USASpending.gov

autocomplete_naics

Read-only

Autocomplete lookup for NAICS codes.

Accepts partial codes ('541') or keywords ('software'). Returns matching
NAICS entries with code and description.

Minimum 2 characters required. Short queries silently match substrings
inside parenthetical notes (e.g. 'x' matches 'except') and produce
nonsense results, so we require 2+ chars.

exclude_retired defaults to True. The upstream NAICS taxonomy still
returns codes retired in 2012/2017/2022; these are almost never what
callers want. Set exclude_retired=False to include them.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`search_text`	Yes
`exclude_retired`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), and the description adds real behavioral detail beyond them: the 2-character minimum, the silent substring matching inside parenthetical notes that produces nonsense results, and the upstream taxonomy returning codes retired in 2012/2017/2022. These are exactly the gotchas an agent needs.

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?

Four short paragraphs, front-loaded with the core purpose before edge-case detail. The parenthetical-note warning is slightly verbose but justified as a real pitfall; overall low waste.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations cover safety. The only meaningful gap is the undocumented 'limit' parameter; everything else an agent needs to invoke the tool correctly is present.

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 0%, so the description must compensate. It does well for search_text (partial codes or keywords) and exclude_retired (default, rationale, and how to override), but says nothing about the 'limit' parameter, which remains opaque in both schema and description.

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 (autocomplete lookup) and resource (NAICS codes), and clarifies the accepted input forms (partial codes like '541' or keywords like 'software'). The NAICS resource is unambiguous against siblings such as autocomplete_awarding_agency, autocomplete_cfda, and autocomplete_psc.

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

Usage Guidelines3/5

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

The description explains how to use the tool (2+ chars, partial code vs keyword input, exclude_retired default) but gives no explicit guidance on when to choose it over siblings like get_naics_details or get_def_codes_reference. Usage context is implied rather than spelled out.

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

All USASpending.gov tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.