Skip to main content
Glama
Gov Tenders & Grants MCP

Gov Tenders & Grants MCP

USAspending API Awards: federal contract and grant awards

publicrecords--usaspending-awards-scraper
Read-only

Search federal contract and grant awards to identify who won and for how much by agency, recipient, NAICS, or date, returning award IDs and source links.

Instructions

USAspending API Awards: federal contract and grant awards. Who won federal contracts and grants, and for how much? Pulls USAspending awards by agency, recipient, NAICS and period, with award IDs and source links.

When to use: Use when you need who won US federal contracts and grants and for how much (USAspending), by agency, recipient, NAICS or period.

Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset.

Behavior: starts one run of the Apify Actor "publicrecords/usaspending-awards-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/publicrecords/usaspending-awards-scraper

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "publicrecords--usaspending-awards-scraper"
  }
}

Input Schema

NameRequiredDescriptionDefault
naicsNoMapped to filters.naics_codes.
agencyNoToptier awarding agency name → filters.agencies[{type:awarding,tier:toptier,name}]. Example: Department of Defense.
endDateNoYYYY-MM-DD. Default: today.
keywordsNoMapped to filters.keywords. Leave empty for broad recent awards; prefer agency/recipient/date.
maxItemsNoCap on award rows (deduped by awardId|generatedInternalId).
recipientNoMapped to filters.recipient_search_text (array). Example: Boeing. Verified shape requires an array of strings.
startDateNoYYYY-MM-DD. Default: today − 30 days (recent awards window).
subawardsNoPass subawards flag to search (default false).
awardTypesNoDefault A,B,C,D (contracts/IDVs). Avoid assistance codes that may list individuals.
fetchDetailsNoHydrate via GET /awards/{generated_internal_id}/.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare read-only, non-destructive, open-world behavior, so the bar is lower, yet the description still adds real operational context: it starts one run of the Apify Actor via the hosted MCP gateway, requires the caller's own APIFY_TOKEN, and bills against their Apify account. It also discloses that results come back as dataset rows plus run/dataset IDs for paging, and links the source docs.

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?

Well structured and front-loaded: a summary sentence, then labeled 'When to use', 'Returns', 'Behavior', and 'Docs' sections. There is minor redundancy, since 'federal contract and grant awards' is repeated in the title and the first sentence, but nothing is wasted overall.

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 10-parameter, zero-required scraper with no output schema, the description covers the essential gaps: what the run produces, that rows map one-per-result, and how to page the full dataset via run/dataset IDs. It does not touch on cost/credit consumption or run duration, which are the remaining unknowns for an agent invoking a paid Actor run.

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?

Schema description coverage is 100%, so every parameter is already documented in the schema, which sets the baseline at 3. The description only restates the same dimensions ('by agency, recipient, NAICS and period') and adds no syntax, precedence, or interaction guidance (for example how keywords interact with agency/recipient filters) beyond what the schema already provides.

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?

States a specific verb and resource: 'Pulls USAspending awards by agency, recipient, NAICS and period, with award IDs and source links.' The domain (USAspending federal awards) is concrete enough to separate it from the tender/meeting siblings, though it never explicitly contrasts itself with publicrecords--grants-gov-scraper, which covers adjacent grant data.

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?

A dedicated 'When to use' block gives a clear trigger: 'when you need who won US federal contracts and grants and for how much... by agency, recipient, NAICS or period.' It gives positive context but no exclusions or named alternatives for the overlapping siblings, so it stops short of full routing guidance.

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