Skip to main content
Glama
@corridordata/mcp-server

@corridordata/mcp-server

Official
by corridordata

search_us_federal_awards

Read-onlyIdempotent

Find companies that recently won U.S. federal prime contracts or grants via USAspending.gov, filtered by keyword, NAICS code, and minimum USD value, with enriched company domains.

Instructions

Find companies that recently won US federal prime contracts or grants via USAspending.gov v2 API filtered by keyword, NAICS code, and minimum USD value with enriched company domains (corridordata/usaspending-federal-contract-awards).

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": "search_us_federal_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysBackNoLookback window in days.
keywordsNoKeywords matched against award descriptions (e.g. ['cybersecurity', 'cloud']).
maxItemsNoMaximum federal contract or grant award records to return.
naicsCodesNoOptional 2-to-6 digit NAICS prefixes (e.g. ['541511', '541512']).
awardCategoryNoQuery prime Federal Contracts or Federal Grants.contracts
maxTotalChargeUsdNoOptional per-run USD spend cap forwarded to Apify Pay-Per-Event billing (`maxTotalChargeUsd`).
minAwardAmountUsdNoMinimum obligated award amount in USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered. The description adds value beyond them by disclosing the upstream data source, the specific dataset identifier, and that results are enriched with company domains. It does not, however, mention that runs are metered (the Apify pay-per-event charge cap implied by maxTotalChargeUsd), which is a behavioral trait an agent might care about.

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?

A single front-loaded sentence with the action, source and filters in order, and no filler. The trailing parenthetical dataset identifier and enrichment note are compact, though the sentence is dense enough that the filter list competes with the core purpose.

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?

With seven optional parameters, full schema coverage and annotations carrying the safety profile, the description supplies the missing upstream-source and enrichment context. It stops short of describing the shape of returned records (company, award amount, agency, domain) and any result-count behavior, which matters somewhat given there is no output schema.

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 with defaults, ranges and examples. The description reinforces keyword, NAICS and minimum USD filtering plus the recency window, but adds no format or interpretation detail beyond the schema – the standard baseline applies.

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 uses a concrete verb and resource ('Find companies that recently won US federal prime contracts or grants'), names the upstream source (USAspending.gov v2 API), and lists the three filters that define the query. The 'US federal' scope plus contracts-or-grants framing clearly separates it from the sibling tools covering EU/Spain/UK grants, jobs, tenders and SEC filings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the phrase 'recently won' and the keyword/NAICS/minimum-value filters signal the prospecting use case, but there is no explicit when-to-use, when-not-to-use, or named alternative among the grant/tender siblings. An agent must infer selection from the domain scope alone.

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