Skip to main content
Glama

Browse industry and product codes

browse_codes
Read-onlyIdempotent

Browse what the government buys, with contract spend. kind: psc (products and services) | naics (industries). No group and no query -> the groups (PSC: services by letter, e.g. D = IT services, R = professional support; products by 2 digits, e.g. 84 = clothing and individual equipment; NAICS: 2-digit sectors), largest first. group -> the codes in it. query -> codes whose name contains the words. Default year: last complete fiscal year. Use a code or its name in a plan's psc / naics filter.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNopsc (products and services) or naics (industries).psc
groupNoA group to list the codes in: a PSC letter or 2-character group (e.g. "D", "84") or a 2-digit NAICS sector (e.g. "54").
limitNoMost rows to return, 1-200.
queryNoWords in a code's name, e.g. "body armor", "janitorial".
fiscal_yearNoFederal fiscal year (October-September), e.g. 2025; default the last complete one.

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": "browse_codesDictOutput",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the description only needs to add operational detail. It does: results are ordered largest first, and the year defaults to the last complete fiscal year. It adds no rate-limit, pagination, or truncation caveats beyond what the schema's limit field implies.

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?

Purpose is front-loaded and the arrow notation makes the three input modes scannable, with no filler sentences. The dense pipe/arrow shorthand is slightly cryptic on a first read and takes a moment to parse compared to plain prose.

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?

With a full output schema and rich annotations, the description carries only what structured fields cannot: mode behavior, default fiscal year, and ordering. The main residual gap is routing guidance relative to search_codes, which matters for a zero-required-parameter tool an agent could easily confuse with a search sibling.

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 meaning: it explains that omitting group and query switches the tool from returning codes to returning groups, and it spells out the group taxonomy per kind (PSC letters like D = IT services, 2-digit product groups like 84, 2-digit NAICS sectors like 54). That mode-switching semantics goes beyond field-level schema text.

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?

States a concrete verb and resource — browsing government product/service and industry codes with contract spend — and lists what each `kind` value represents. An agent can grasp the domain and outputs, but the description never distinguishes this from the sibling search_codes, so the browse-vs-search boundary is left to inference.

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?

Explicitly maps input combinations to behavior: no group and no query returns groups, group returns the codes within it, query filters by name. It also states the downstream purpose ('Use a code or its name in a plan's psc / naics filter'). It does not say when to prefer search_codes or another sibling instead, so no exclusions are given.

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