API Ninjas

getNaics

Read-only

Returns the official title, description, full hierarchy, index terms and cross-references for a NAICS code. Pass crosswalk_to to also map the code to another NAICS revision or to SIC. Available on all plans.

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": "getNaics"
  }
}

Input Schema

Name	Required	Description	Default
`code`	No	NAICS code, 2 to 6 digits. Required unless title is provided.
`year`	No	NAICS revision. Currently 2022 only; NAICS 2027 is not published by the Census Bureau until January 2027.	2022
`codes`	No	Comma-separated NAICS codes for batch lookup. Maximum 50 on Developer, 500 on Business and above.
`title`	No	Look up by official title. Supports partial matching.
`country`	No	Currently US only. NAICS Canada and SCIAN Mexico are not yet available.	US
`crosswalk_to`	No	Also map the code to an earlier NAICS revision. Currently 2017 only. The Census concordance covers 6-digit national industries.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 9, 2026

TDQS

B3.2/5.0

Behavior3/5

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

readOnlyHint=true already establishes the safe-read profile, so the description is not the primary carrier. It does add real context beyond annotations: the full list of returned fields and the crosswalk behavior (mapping to an earlier revision or SIC), plus plan availability. It omits batch semantics even though a batch parameter exists.

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 compact sentences, front-loaded with the payload of the response and followed by the optional mapping behavior. The closing 'Available on all plans' is terse but useful commercial context rather than filler.

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 no output schema, the description correctly compensates by enumerating the returned fields (title, description, hierarchy, index terms, cross-references). It leaves the batch path and batch limits to the schema, which is reasonable, so the definition is essentially complete for a read-only lookup.

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 every parameter including code, year, title, country and crosswalk_to is documented in the schema itself. The description's crosswalk sentence largely restates the schema's crosswalk_to description, adding no syntax or constraint detail beyond it, so the baseline 3 applies.

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 names a specific verb and resource (returns NAICS code data) and enumerates the returned content: official title, description, hierarchy, index terms, cross-references. However, it does not differentiate from the sibling searchNaics, which also deals with NAICS codes, forcing the agent to infer the lookup-vs-search split.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance or routing to alternatives. The mention of crosswalk_to describes a parameter, not a usage condition, and with four NAICS siblings (searchNaics, classifyNaics, getNaicsRisk, getNaicsSizeStandard) the agent has no stated rule for picking this one.

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

All API Ninjas 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.

Resources

Need Help?