Skip to main content
Glama
GovCon API MCP

GovCon API MCP

Official

Search federal contracting data

search
Read-onlyIdempotent

Query one GovCon dataset with validated filters to discover opportunities, awards, contracts, entities, subawards, protests, and compliance records.

Instructions

Search one dataset. filters holds that dataset's filters; an unknown filter is refused with the list of valid ones. 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, solicitation_number (exact: every notice in one procurement), content (Pro: words inside the attached documents), fields (comma-separated columns, e.g. "notice_id,title,response_deadline" for a cheap scan); sort_by: posted_date | due_date | award_amount | title | agency | relevance; sort_order: asc | desc

  • 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_after_months, ends_within_months, date_anchor (current_end | potential_end), options_exhausted_only, amount_min, early_signal_days (1-365, default 180; 7-30 keeps the market-level early_signals short), early_signal_types; sort_by: ends_soonest | value | mod_churn | de_obligated

  • companies (Pro): firms with award history, by name. q (name, REQUIRED), naics, agency, naics_small. Ranking firms without a name ("who wins this work") is partners

  • 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): firms ranked by dollars won (FY2025 onward) in a NAICS, agency, state or PSC: who wins this work, the incumbents, teaming candidates. 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

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": {
      "dataset": "<dataset>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
datasetYes
filtersNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.4

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds real operational context on top: unknown filters are rejected with the list of valid ones, rows are large so `limit` should stay 20-50 with `offset` paging, several datasets require the Pro plan, and dates are YYYY-MM-DD. It stops short of auth requirements or rate limits, but the error and pagination behavior is well disclosed.

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?

It is long, but it is front-loaded with general rules (filter validation, resolve(), dates, Pro, pagination) followed by a scannable per-dataset bullet list where each line is dense and functional. Given a freeform `filters` object with zero schema docs, nearly every token carries payload; only minor enumeration of enum values could be trimmed.

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 tool fronting 17 datasets with an undocumented open `filters` bag, the description supplies everything needed to call it correctly: dataset selection semantics, valid filter keys and formats, pagination behavior, plan gating, and rejection behavior. Return values need not be described because an output schema exists.

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 coverage is 0% (schema only lists the dataset enum and two untyped ints plus an open `filters` object), so the description carries the entire burden and does: it specifies allowed filter keys per dataset, value formats and enums (set_aside, notice_type, award_type_code, idv_type, sort_by/sort_order), which filters are required (since, q, naics, state), and the meaning of limit/offset.

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?

"Search one dataset" is a specific verb+resource, and the description then enumerates all 17 datasets with a one-line characterization of each (SAM.gov notices, FPDS awards, GAO protests, SAM registrations), so an agent knows exactly what corpus it is querying. It also routes away from siblings where relevant, e.g. agency/NAICS/UEI values come from resolve(), and naming firms without a name is partners.

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?

Explicit routing rules are embedded throughout: use `parent_piid` on contracts to find a vehicle's orders, find a vehicle PIID via contracts or the notice, use partners rather than companies when no name is known, and use resolve() before filtering by agency/naics/uei. It also sets exclusions ("Only opportunities, forecasts and partners take `keywords`"; opportunity_changes takes no other filters) and flags plan gating with (Pro).

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