Skip to main content
Glama

Find NAICS codes for a business

naics_finder
Read-onlyIdempotent

Describe the work in plain words -> the NAICS codes buyers actually use for it (codes on SAM.gov notices whose titles have the words and on federal contracts described with them), each with its SBA size standard.

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

Input Schema

NameRequiredDescriptionDefault
descriptionYesThe work in plain words, e.g. "commercial janitorial and floor care" or "drone mapping surveys".

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

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. Beyond that, the description discloses real methodology value: codes are grounded in SAM.gov notice titles and federal contract descriptions, which tells the agent the results are usage-based rather than a pure taxonomy lookup.

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?

One sentence, front-loaded with the input and output mapped by an arrow, with the parenthetical carrying the provenance rationale. Dense but every clause earns its place; the nested parenthetical is the only readability cost.

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?

For a one-parameter read-only tool with an output schema and full annotation coverage, the description supplies what is needed: input form, output content (codes plus size standards), and the data source scope (SAM.gov notices and federal contracts). Only minor gaps remain on result limits or ranking.

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?

With a single parameter at 100% schema coverage and two concrete examples already in the schema, the description's 'work in plain words' framing adds only modest meaning beyond it. Baseline 3 applies since the schema does the heavy lifting.

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 output: turn a plain-language work description into 'the NAICS codes buyers actually use,' each with its SBA size standard. This distinguishes it from code-browsing siblings (browse_codes, search_codes) by its natural-language, evidence-based input, though it never names those siblings explicitly.

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 through the arrow formulation ('Describe the work in plain words -> ...') and the schema examples, so an agent can infer this is the entry point when starting from prose rather than a known code. There is no explicit when-not-to-use guidance or routing to size_standard / search_codes for follow-ups.

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