Skip to main content
Glama

Get Company NAICS Code

get_company_naics_code
Read-only

Returns the company's NAICS (North American Industry Classification System) code, with its title and sector: the code saved on the company, or else its industry's code. A message instead means the company has no industry on file yet. Answer in plain language and never show the user the field names.

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

Input Schema

NameRequiredDescriptionDefault
contextNoOptional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details.
llm_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a safe, closed-world read, so the description's job is to add on top, and it does: it discloses the precedence logic between the stored code and the industry code, plus the message-shaped empty state. It also imposes a presentation constraint (plain language, never expose field names), which is genuinely non-obvious behavior. No pagination or auth caveats are needed for a single-record read.

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 return contract and fallback rule are front-loaded in the first sentence, with the empty-state note and formatting instruction following. Every sentence carries information, though the formatting directive could be slightly tighter.

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 must convey the return shape, and it does: code, title, sector, plus what an error-like message means. For a zero-required-parameter read tool this covers what an agent needs; only the choice among sibling getters is left unaddressed.

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?

All three parameters are optional analytics fields fully documented in the schema (100% coverage), and the description adds nothing about them. Baseline 3 is correct since the schema carries the entire burden and there is no friction an agent would hit.

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?

Names a specific resource (the company's NAICS code) and the exact payload returned: code, title, and sector. It also states the fallback rule (company's saved code, otherwise the industry's code), which makes the result unambiguous. It stops short of naming which sibling getter to prefer, but the verb+resource is clear enough to select without opening the schema.

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 rather than stated: use it when the user needs the company's industry classification. The description does describe one important edge condition, that a message means no industry is on file, which helps interpret an empty answer. There is no explicit when-not or pointer to alternatives such as get_company_info.

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.