Skip to main content
Glama

Search agencies, industries and product codes

search_codes
Read-onlyIdempotent

Look up codes and official names. kind: agency | bureau | state | county | naics | psc | program. Matches names (substring, case-insensitive) or code prefixes. Plans can use either the names or the codes.

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": {
      "kind": "<kind>",
      "query": "<query>"
    },
    "name": "search_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesWhat to look up: agency, bureau (sub-agency), state, county, naics (industry), psc (product or service code) or program (Assistance Listing).
limitNoMost rows to return, 1-50.
queryYesWords in the name, or the code itself, e.g. "veterans affairs", "541511", "D302".

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "title": "search_codesDictOutput",
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare this as a read-only, idempotent, non-destructive, closed-world search. The description adds useful matching behavior beyond that: names are matched by case-insensitive substring and codes by prefix. It does not describe result ordering or pagination behavior beyond the limit parameter.

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?

The description is short and front-loaded, with the core action stated first. It is mostly efficient, though the inline kind list duplicates the enum values already documented in the schema.

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?

Given the rich annotations, 100% schema coverage, and an output schema, the definition provides enough context for a simple read-only code lookup. The main remaining gap is the absence of sibling-tool routing guidance, which is more of a usage-guideline issue than a completeness failure.

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 input schema already documents kind, query, and limit thoroughly. The description reinforces that query may be either a name or a code and clarifies substring/prefix matching, but it largely repeats enum and example information already present in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: 'Look up codes and official names.' It scopes the lookup to seven named kinds, so the agent knows this is a reference search across agencies, geographies, industries, and codes. It does not explicitly distinguish this tool from siblings such as browse_codes or naics_finder.

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?

Usage is implied by the kind list and by the note that plans can use either names or codes. However, there is no explicit when-to-use guidance and no mention of when to prefer browse_codes, naics_finder, or other sibling search tools. The agent must infer the appropriate context.

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.

Resources