Skip to main content
Glama
Bosco Labs Data

Bosco Labs Data

Official

Pentagon (DoD) contract awards

search_dod_contract_awards
Read-only

Query US defense and federal contract awards since FY2008 to find who won, obligated amounts, awarding agency, recipient ticker, and NAICS/PSC industry codes, with source links.

Instructions

US Department of Defense contract awards (or any other federal agency's) since FY2008: who won, how much was obligated, which service, the parent company and the winner's US stock ticker with SEC shares outstanding (source: USAspending.gov / FPDS, tickers from the SEC). Use it for "which contracts did Lockheed/Kratos win", the largest recent Pentagon awards, or awards in an industry (NAICS/PSC).

Default: DoD award-days of at least $7.5M (the DoD's public announcement threshold),
signed in the last 135 days. DoD data is published with a delay of up to ~3 months, so
the most recent weeks are incomplete. Newest signing dates first, then largest amounts.
Slow: a call can take a minute or more, so keep max_results small.

Returns one row per award per signing day: action_date, recipient_name, parent_name,
ticker, amount_usd (summed obligations that day), new_award, awarding_agency,
awarding_sub_agency, award_id, naics_description, psc_description, description
(shortened), shares_outstanding and usaspending_url (the award page; cite it).

Cost to the user: $0.005 per award row returned.

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_dod_contract_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNo
tickersNo
agenciesNoTop-tier agency; omit for DoD; e.g. "Department of Homeland Security"
date_fromNoSigning date; default: 135 days before date_to
psc_codesNoProduct/service codes, e.g. 1410, R425
recipientsNoWinner or parent name contains, e.g. "kratos"
max_resultsNoMax award rows to return (1-50).
naics_codesNoIndustry codes, e.g. 336414
min_amount_usdNoMin obligated per award and day

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the publishing lag (up to ~3 months, so recent weeks are incomplete), the sort order (newest signing date, then largest amount), the latency warning (a call can take a minute or more), and the per-row cost ($0.005/award). These are exactly the facts an agent needs that annotations cannot convey.

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?

The description is front-loaded with purpose, then defaults, then behavior and cost — a sensible ordering. The one wasteful element is the enumerated list of returned fields (action_date, recipient_name, ticker, ...), which duplicates the existing output schema and 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 slow, paid, open-world search with nine optional parameters and an output schema, the definition covers scope, defaults, latency, data freshness, result grain, cost, and citation guidance. Nothing an agent needs to call it correctly and interpret the response is missing.

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?

Schema coverage is 78%, so the schema does most of the work, but the description adds real meaning: the rationale and value of the $7.5M / 135-day defaults, the guidance to keep max_results small, and examples of industry (NAICS/PSC) and ticker filtering. It does not add syntax details for agencies or recipients beyond the schema, hence not a 5.

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 names a specific resource (US DoD contract awards, extendable to any federal agency) with a stated time span (since FY2008), data source (USAspending.gov / FPDS, tickers from SEC), and the exact fields returned. An agent can immediately distinguish this from SEC-filing or EU-tender siblings without opening the schema.

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 three concrete use cases (contracts won by a named company, largest recent Pentagon awards, awards within an industry via NAICS/PSC) and states the effective default scope: DoD, >= $7.5M, signed in the last 135 days. It does not explicitly say when to prefer an alternative tool, but the domain is unambiguous against the sibling set.

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