Skip to main content
Glama

SignalTender B2B, GovCon & LegalTech MCP Server

Classify NAICS, SIC, Federal PSC & State NIGP/UNSPSC Codes

classify_naics_psc_nigp
Read-onlyIdempotent

Map any company profile, product description, or Statement of Work (SOW) into ranked 6-digit NAICS codes (with official SBA Small Business Size Standards in revenue or headcount), 4-digit SIC codes, 4-character Federal PSC codes, and State NIGP/UNSPSC commodity codes. This is a read-only, stateless taxonomy classification call (requires X-RapidAPI-Key; description_text is required, context_type tunes code selection for vendor KYB profiles vs. RFP scopes, and max_secondary_codes [1-5, default 3] controls how many secondary NAICS/PSC alternatives are returned alongside the primary code). Use this tool whenever you need industry, procurement, or KYB taxonomy codes and SBA small-business size caps; use search_historical_awards instead to query past contract awards once you have a NAICS code, or parse_b2b_contract to extract contract dates and dollar values.

Input Schema

NameRequiredDescriptionDefault
context_typeNoClassification context: 'company_or_vendor_profile', 'rfp_or_sow_scope', or 'product_or_line_item'.company_or_vendor_profile
description_textYesUnstructured text describing a company's offerings, a B2B product catalog, or a government RFP/SOW technical scope (20 to 50,000 characters).
max_secondary_codesNoMaximum number of secondary/alternative NAICS, PSC, and NIGP codes to return in addition to the top-ranked primary code (integer 1 to 5; defaults to 3).

Output Schema

NameRequiredDescriptionDefault
sic_codesNo4-digit Standard Industrial Classification (SIC) codes for FinTech KYB, banking underwriting, and corporate filings.
primary_naicsNoHighest-confidence primary 6-digit NAICS code and SBA Small Business Size Standard.
federal_psc_codesNo4-character Federal Product Service Codes (PSC) for SAM.gov saved searches and FPDS award tracking.
secondary_naics_codesNoAdditional relevant 6-digit NAICS codes for SAM.gov registration and secondary capabilities.
primary_industry_sectorNo2-digit NAICS sector code and name (e.g., '54 - Professional, Scientific, and Technical Services').
kyb_and_procurement_notesNoActionable guidance covering SAM.gov NAICS/PSC profile setup, SBA small-business size standard nuances (e.g., 150-employee IT Value Added Reseller footnote under 541519), SLED NIGP registration, and KYB risk classification.
entity_or_offering_summaryNoConcise 1-sentence executive summary of the company, SOW, or product analyzed.
state_unspsc_and_nigp_codesNo8-digit UNSPSC and 5-digit NIGP Class-Item codes for State/Municipal SLED vendor portals and ERP catalogs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / properties / context_type / description
      Previous value: -"Input context mode: 'company_or_vendor_profile' (default, optimizes for SAM.gov vendor registration & FinTech KYB SIC/NAICS), 'rfp_or_sow_scope' (optimizes for solicitation set-aside NAICS & Federal PSC), or 'product_or_service_catalog' (emphasizes NIGP/UNSPSC commodity codes)."New value: +"Classification context: 'company_or_vendor_profile', 'rfp_or_sow_scope', or 'product_or_line_item'."
    • changedInput schema / properties / context_type / enum
      Previous value: -[
      -  "company_or_vendor_profile",
      -  "rfp_or_sow_scope",
      -  "product_or_service_catalog"
      -]New value: +[
      +  "company_or_vendor_profile",
      +  "rfp_or_sow_scope",
      +  "product_or_line_item"
      +]
    • addedOutput schema / properties / entity_or_offering_summary
      Added value: +{
      +  "description": "Concise 1-sentence executive summary of the company, SOW, or product analyzed.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / federal_psc_codes / description
      Previous value: -"Matched 4-character Federal Product Service Codes (PSC)."New value: +"4-character Federal Product Service Codes (PSC) for SAM.gov saved searches and FPDS award tracking."
    • addedOutput schema / properties / kyb_and_procurement_notes
      Added value: +{
      +  "description": "Actionable guidance covering SAM.gov NAICS/PSC profile setup, SBA small-business size standard nuances (e.g., 150-employee IT Value Added Reseller footnote under 541519), SLED NIGP registration, and KYB risk classification.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / primary_industry_sector
      Added value: +{
      +  "description": "2-digit NAICS sector code and name (e.g., '54 - Professional, Scientific, and Technical Services').",
      +  "type": "string"
      +}
    • changedOutput schema / properties / primary_naics / description
      Previous value: -"Top-ranked 6-digit NAICS code, title, confidence score, and official SBA Small Business Size Standard."New value: +"Highest-confidence primary 6-digit NAICS code and SBA Small Business Size Standard."
    • changedOutput schema / properties / secondary_naics_codes / description
      Previous value: -"Up to max_secondary_codes alternative 6-digit NAICS classifications."New value: +"Additional relevant 6-digit NAICS codes for SAM.gov registration and secondary capabilities."
    • changedOutput schema / properties / sic_codes / description
      Previous value: -"Matched 4-digit Standard Industrial Classification (SIC) codes."New value: +"4-digit Standard Industrial Classification (SIC) codes for FinTech KYB, banking underwriting, and corporate filings."
    • changedOutput schema / properties / state_unspsc_and_nigp_codes / description
      Previous value: -"Matched State SLED NIGP and 8-digit UNSPSC commodity codes."New value: +"8-digit UNSPSC and 5-digit NIGP Class-Item codes for State/Municipal SLED vendor portals and ERP catalogs."
  2. Changed8 schema fields changed
    • addedInput schema / properties / context_type / description
      Added value: +"Input context mode: 'company_or_vendor_profile' (default, optimizes for SAM.gov vendor registration & FinTech KYB SIC/NAICS), 'rfp_or_sow_scope' (optimizes for solicitation set-aside NAICS & Federal PSC), or 'product_or_service_catalog' (emphasizes NIGP/UNSPSC commodity codes)."
    • changedInput schema / properties / description_text / description
      Previous value: -"Company profile, product description, or Statement of Work text."New value: +"Unstructured text describing a company's offerings, a B2B product catalog, or a government RFP/SOW technical scope (20 to 50,000 characters)."
    • addedInput schema / properties / description_text / maxLength
      Added value: +50000
    • addedInput schema / properties / description_text / minLength
      Added value: +20
    • addedInput schema / properties / max_secondary_codes / description
      Added value: +"Maximum number of secondary/alternative NAICS, PSC, and NIGP codes to return in addition to the top-ranked primary code (integer 1 to 5; defaults to 3)."
    • addedInput schema / properties / max_secondary_codes / maximum
      Added value: +5
    • addedInput schema / properties / max_secondary_codes / minimum
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "federal_psc_codes": {
      +      "description": "Matched 4-character Federal Product Service Codes (PSC).",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "primary_naics": {
      +      "description": "Top-ranked 6-digit NAICS code, title, confidence score, and official SBA Small Business Size Standard.",
      +      "type": "object"
      +    },
      +    "secondary_naics_codes": {
      +      "description": "Up to max_secondary_codes alternative 6-digit NAICS classifications.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "sic_codes": {
      +      "description": "Matched 4-digit Standard Industrial Classification (SIC) codes.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "state_unspsc_and_nigp_codes": {
      +      "description": "Matched State SLED NIGP and 8-digit UNSPSC commodity codes.",
      +      "items": {
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and stateless behavior, so the safety profile is covered. The description adds one genuinely non-redundant fact — it requires an X-RapidAPI-Key — but says nothing about return format, rate limits, or failure modes, and the output schema carries the return shape.

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?

Front-loaded with the outputs and scoping, then parentinghetical parameter detail, then an explicit routing sentence to alternatives. Dense and largely waste-free, though the single long sentence packing all parameters is heavy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't explain return values; together with the auth note, param intent, and explicit sibling routing, an agent has everything needed to select and invoke this tool correctly.

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 goes beyond the schema by explaining that context_type 'tunes code selection for vendor KYB profiles vs. RFP scopes' and that max_secondary_codes controls secondary NAICS/PSC alternatives returned. It omits the 'product_or_line_item' nuance, keeping it short of a 5.

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

Purpose5/5

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

States a specific verb ('Map') and enumerates the exact resource outputs: ranked 6-digit NAICS with SBA size standards, 4-digit SIC, 4-character Federal PSC, and NIGP/UNSPSC codes. This is clearly distinguishable from siblings like search_historical_awards or parse_b2b_contract.

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

Usage Guidelines5/5

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

Explicitly says to use this tool 'whenever you need industry, procurement, or KYB taxonomy codes and SBA small-business size caps,' then names two alternatives and the conditions that select them (search_historical_awards once you have a NAICS code; parse_b2b_contract for dates/dollar values).

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.