Skip to main content
Glama
govconapi

io.github.govconapi/govconapi

Official

Get NAICS Market

get_naics_market
Read-onlyIdempotent

Retrieve a federal market profile for any NAICS code—spending, competition, set-aside leverage, top buyers, and top incumbents—to assess market opportunity before bidding.

Instructions

Get the federal market profile for one NAICS code: spending, competition, set-aside leverage, top buyers, and top incumbents.

Market Research tool, the AWARD side of a market (who's winning, how much). Pair with
get_naics_positioning for the SOLICITATION side (the language contracting officers
use), get_naics_simplified_acquisition for the small-buy value bands, and
get_naics_competition for the deeper contestability read.

- code: 2-6 digit NAICS code

`size_standard` is null (`size_standard_status: "pending_sba_table"`), the SBA
small-business size threshold isn't part of this dataset. Check SBA's table directly
for small-business eligibility rather than relying on this response for it.

Free tier. 404 if there's no FY2025+ federal contract activity for this code.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses important behavioral caveats: size_standard is null with a 'pending_sba_table' status, users should check SBA directly for small-business eligibility, and a 404 occurs when there is no FY2025+ contract activity. These are non-obvious response behaviors an agent needs.

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?

Every sentence earns its place: the core purpose is front-loaded, sibling distinctions follow, the parameter is documented, and response caveats are clearly appended. It is dense but not bloated.

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?

For a single-parameter read tool with an output schema already present, the description covers purpose, parameter format, sibling alternatives, data caveats, and error behavior. Nothing essential is missing for correct invocation.

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?

The schema only defines 'code' as a required string with 0% description coverage. The tool description compensates by specifying '2-6 digit NAICS code', adding format and range meaning beyond the raw schema.

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?

Description states a specific verb and resource: 'Get the federal market profile for one NAICS code' and enumerates the output contents (spending, competition, set-aside leverage, top buyers, top incumbents). It also differentiates itself from siblings by labeling itself the 'AWARD side' of a market.

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?

Provides explicit pairing guidance with sibling tools: get_naics_positioning for the solicitation side, get_naics_simplified_acquisition for small-buy bands, and get_naics_competition for contestability. This tells an agent exactly when to choose this tool over alternatives.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/govconapi/govconapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server