F
license-
qualityC
maintenanceScreens DIBBS RFQs for micro-purchase viability using deterministic logic without LLM calls.
Compliance Batch Alignment
Server Details
Check whether a NAICS code aligns with a vertical: a routing-for-review signal, not a determination.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.9/5.0
Tool DescriptionsA
Average 4/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
With only one tool, there is no possibility of confusing it with another. The tool's purpose is clearly described: it aligns a NAICS code with a business vertical and returns a result along with the mapping. No ambiguity exists.
Naming Consistency5/5
The single tool name 'naics_align' is internally consistent, though it follows a noun-verb order rather than the more common verb-noun. Since there are no other tools to create a pattern, naming is consistent by default.
Tool Count2/5
The server is called 'Compliance Batch Alignment' but provides only one tool that handles a single NAICS code alignment. This is too few for the apparent batch-oriented scope, making the tool count feel significantly thin and under-featured.
Completeness2/5
The tool covers a single alignment check but lacks any batch processing capability, which is implied by the server name. There are also no utilities for listing verticals or retrieving NAICS mappings, leaving notable gaps for a compliance alignment workflow.
Available Tools
1 toolnaics_alignAInspect
Given a NAICS code and a business vertical, return whether the code's mapped (Bonis known-commerce) description aligns with the vertical, that description, and an alignment band. Pure, local, no PII. Information, not a compliance determination.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| vertical | Yes | The stated business vertical/industry. | |
| naics_code | Yes | The NAICS code (digits). |
Tool Definition Quality
A4/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It discloses that the operation is 'Pure, local, no PII' and provides an informational output, not a compliance determination. It also names the output components. It does not cover invalid input handling, but for a read-only tool this is reasonable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loads the core function ('Given a NAICS code and a business vertical, return whether...'), and includes clarifying parentheticals ('Bonis known-commerce', 'Information, not a compliance determination'). Every sentence earns its place with no redundancy.
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 two-parameter, read-only tool with no output schema, the description covers the essential context: inputs, output components, and important caveats (local, no PII, informational only). It does not detail return format or edge cases, but given the low complexity and full schema coverage, this is sufficient.
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?
The schema descriptions already fully cover both parameters ('NAICS code (digits)' and 'The stated business vertical/industry'), so schema coverage is 100%. The description adds no additional semantic detail beyond restating the inputs, so the baseline of 3 is appropriate.
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 clearly states the tool's operation: given a NAICS code and vertical, it returns alignment status, the mapped description, and an alignment band. This is a specific verb+resource pairing, though there are no siblings to differentiate from, and the phrase 'that description' is slightly ambiguous.
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?
The description implies appropriate usage: use for informational alignment checks when you have a NAICS code and vertical. It explicitly states it is 'not a compliance determination,' giving a clear exclusion. No alternatives are mentioned, but the context is sufficient for this simple tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityCmaintenanceScreens names against the US Consolidated Screening List including OFAC SDN and BIS Entity List, keyless.2MIT
- AlicenseAqualityAmaintenanceSearch 419,000+ LLM-extracted space regulatory filings from the FCC, ITU, UNOOSA, and FAA. Semantic search, entity dossiers, spectrum-band holdings, launch licenses, filing trends, and alerts.211MIT
- Flicense-qualityBmaintenanceEnables competitive analysis by validating companies, identifying sectors and top competitors, and generating comparative reports with actionable insights.