Skip to main content
Glama
GovCon API MCP

GovCon API MCP

Official

Analyze a NAICS market

market
Read-onlyIdempotent

Analyze NAICS code size, competition, set-aside mix, small-buy share, and solicitation language to see who wins federal contracts and how agencies buy. Find codes by traits.

Instructions

How big a NAICS market is, who wins it, and how it buys, across every agency. A 6-digit naics for the per-code views, which take no filters (for one agency: search(contracts) with naics and agency).

  • size: obligated dollars, award count and concentration

  • competition: offers per award, single-bidder share, set-aside mix

  • solicitation_language: the phrases contracting officers use in that market's notices

  • small_buys: how much is bought under the micro-purchase and simplified-acquisition thresholds

  • leaderboard: ranked NAICS codes; board = biggest, least_crowded, most_open (no naics needed)

  • find_codes: NAICS codes by market traits; filters: keywords (matches NAICS titles, not topics: use "computer", not "cybersecurity"), sector, prefix, min_market, max_competitors, set_aside_family (total_small_business | 8a | sdvosb | wosb | hubzone), sort_by (market | competitors | setaside_pct)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "view": "<view>"
    },
    "name": "market"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
boardNo
naicsNo
filtersNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real operational context beyond that: per-code views ignore filters, keywords match NAICS titles rather than subject topics ("computer" not "cybersecurity"), and the leaderboard accepts named boards. Return values are covered by the output schema, so omitting them is not a gap.

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 core scope sentence, then a tight bullet per view with no filler. Density occasionally costs clarity, since entries like "biggest, least_crowded, most_open" and "concentration" are compressed shorthand, but every line carries information an agent needs.

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?

This is a complex multi-view analytical tool, and the definition covers all six views plus their inputs without restating schema or return values. What is missing is minor but real: no statement of which filters apply to which view, no format hints for sector/prefix/min_market, and no note on result limits given the open-world scope.

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?

With 0% schema description coverage, the description carries the full burden and largely meets it: it explains the role of each `view` enum value, the meaning of `naics` as a 6-digit code, the three `board` values, and enumerates filter keys with the allowed set_aside_family and sort_by values. The gaps are `sector`, `prefix`, and `min_market`, whose expected formats and units are never stated, and `filters` is a free-form object whose keys are only partly specified.

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?

Opening sentence states a specific analytical verb set and resource: market size, share of wins, and buying behavior across all agencies for a NAICS code. It then enumerates the six views by name and tells the agent it is not the agency-filtered case, naming `search(contracts)` with naics and agency as the substitute, which distinguishes it from the sibling `search`.

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?

It gives an explicit routing rule: use a 6-digit `naics` for per-code views, which take no filters, and use `search(contracts)` with naics plus agency when scoping to one agency. It also says `board` needs no naics. It stops short of stating which view to pick for a given question beyond the one-line purposes, and does not say what happens if filters are supplied to a per-code view.

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

Deploy Server

Other Tools