Skip to main content
Glama
govconapi

GovCon API MCP

Official
by govconapi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search federal contracting data

search
Read-onlyIdempotent

Query a chosen US federal procurement dataset—opportunities, awards, contracts, entities, subawards, protests, and more—with filters to find records and support market research.

Instructions

Search one dataset. filters holds that dataset's filters; an unknown filter returns the full list. Agency values come from resolve(agency), NAICS codes from resolve(naics), UEIs from resolve(company). Dates are YYYY-MM-DD. (Pro) marks datasets that need the Pro plan. Keep limit small (20-50) and page with offset: rows are large. Only opportunities, forecasts and partners take keywords.

  • opportunities: SAM.gov notices. naics, psc, agency, keywords, state, set_aside (HUBZone, WOSB, 8(a), Veteran, Small Business), notice_type (Solicitation, Combined Synopsis/Solicitation, Presolicitation, Sources Sought, Award Notice), posted_after, due_before, due_after, value_min, value_max; sort_by: posted_date | due_date | award_amount | title | agency | relevance

  • opportunity_changes: notices added or changed since a time. since (ISO timestamp, required); no other filters

  • forecasts: work agencies plan to buy. agency, naics, set_aside, state, est_award_fy, keywords, is_recompete, source (fco | dhs | hhs); sort_by: est_award_fy | est_solicitation_date | value_high | agency

  • award_notices: SAM.gov award announcements. awardee, uei, naics, agency, value_min, value_max, date_from, date_to

  • contracts: FPDS awards. naics, agency, uei, piid, award_type_code (A | B | C | D), date_from, date_to, amount_min, amount_max; sort_by: action_date | current_total_value_of_award | federal_action_obligation | recipient_name. Find a named vehicle's orders with parent_piid

  • vehicles: IDIQs, GWACs, GSA Schedules. Needs one of uei, piid, agency, naics, idv_type (IDC | FSS | BPA | GWAC | BOA); active_only, ceiling_min. No name search: find a vehicle's PIID via contracts or the notice

  • subawards: who subcontracts to whom. prime_uei, sub_uei, sub_name, naics, agency, piid, date_from, date_to, amount_min; sort_by: subaward_action_date | subaward_amount

  • recompetes (Pro): contracts ending soon. naics, agency, set_aside, state, ends_within_months, amount_min; sort_by: ends_soonest | value | mod_churn | de_obligated

  • companies (Pro): firms with award history. q (name, REQUIRED), naics, agency, naics_small

  • entities: every SAM registration. q (name), naics, state, business_type (SAM code: "8W" WOSB, "QF" SDVOSB), naics_small (a NAICS the firm is SBA-small for), active_only

  • expiring_registrations (Pro): SAM registrations about to lapse. within_days, state, naics

  • partners (Pro): teaming partners with past performance. naics, agency, state, psc, keywords, set_aside (sdvosb | vosb | wosb | hubzone | 8a | sdb | minority_owned)

  • protests: GAO bid protests. agency, protester, status (Open | Closed), outcome (Denied | Dismissed | Sustained | Withdrawn), filed_from, filed_to; sort: recent | oldest | filed | due

  • exclusions: debarred or suspended parties. name, uei, cage_code

  • wage_determinations: type (SCA | DBA | CBA), state (2 letters), county, wd_number, active_only

  • wage_determinations_by_location: every determination for a place. state (2 letters, required), county, type

  • offices: contracting offices that buy a NAICS. naics (required); sort: biggest | most_open

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
datasetYes
filtersNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A5/5.0
Behavior5/5

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond annotations: unknown filters return the full filter list, Pro datasets require a paid plan, result rows are large so limit should be kept small and offset used for paging, and some datasets have required filters.

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 long but necessarily so for a 17-dataset search tool. General rules are front-loaded, followed by a structured bulleted dataset reference, and each sentence provides actionable information without filler.

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?

Given the complex dataset surface and filters object, the description supplies the dataset-specific semantics needed to call the tool correctly. Annotations cover safety, and an output schema exists, so return-value details are appropriately omitted.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It does so thoroughly by documenting the dataset enum, listing filters and required filters per dataset, explaining limit/offset usage, and noting special cases like opportunity_changes requiring since and companies requiring q.

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?

The description opens with a specific verb and resource: 'Search one dataset,' then names every dataset available. It also distinguishes this tool from sibling resolve by explaining that agency, NAICS, and UEI values should come from resolve(agency), resolve(naics), and resolve(company).

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?

The description provides explicit per-dataset guidance: which filters each dataset accepts, which filters are required, which datasets support keywords, and when to use alternatives such as resolving identifiers through resolve or finding vehicle PIIDs through contracts/notices. This leaves little ambiguity about when and how to use the tool.

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