Skip to main content
Glama

Dod Contract Announcements

Dod Awards Recent

dod_awards_recent
Read-onlyIdempotent

Most recent US Department of War (formerly Department of Defense) contract award announcements, Pentagon contracts today, this week, or over any recent window, newest first. Every contract of $7.5M or more is announced here on the business day it is signed, which is weeks ahead of the same award appearing in FPDS/USAspending. Filter by military service/agency (ARMY, NAVY, AIR FORCE, DEFENSE LOGISTICS AGENCY, U.S. TRANSPORTATION COMMAND, DEFENSE ADVANCED RESEARCH PROJECTS AGENCY, DEFENSE HEALTH AGENCY, U.S. SPECIAL OPERATIONS COMMAND, and others) and a minimum award amount. Answers "what defense contracts were announced today", "recent DoD/Pentagon contract awards", "who won a defense contract this week".

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "days": 3
    },
    "name": "dod_awards_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days back from today to include (default 7).
limitNoMax awards to return (1-100, default 25).
serviceNoRestrict to one branch/agency, e.g. "ARMY", "NAVY", "AIR FORCE", "DEFENSE LOGISTICS AGENCY". Matched case-insensitively.
min_amountNoOnly awards at or above this dollar amount. Note: on rows where shared_award is true, amount is the combined multi-contractor program value, not one contractor's share.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, and the description layers on genuinely new facts: a hard coverage floor ($7.5M+), the announcement timing relative to contract signing, and a lead of weeks over FPDS/USAspending. Ordering (newest first) is also disclosed, which the annotations do not 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?

Purpose and freshness are front-loaded in the first sentence, and the trailing example questions aid retrieval. The long parenthetical agency roll-call and 'formerly Department of Defense' aside add bulk that could be trimmed without losing selection value.

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 four-optional-parameter read tool with full schema coverage and annotations, the description covers what the data is, how fresh it is, its coverage floor, and how to filter. The one remaining gap is return shape — with no output schema, the agent gets no sense of what fields each award row contains (contractor, amount, shared_award flag), though the schema's min_amount note partially hints at it.

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 100%, so the baseline is 3, but the description adds value by enumerating concrete valid service values (ARMY, NAVY, AIR FORCE, DEFENSE LOGISTICS AGENCY, U.S. TRANSPORTATION COMMAND, DARPA, DHA, SOCOM) that the schema only partly lists. It adds nothing beyond the schema for days and limit, which are already documented.

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?

States a concrete verb and resource (most recent DoD/Pentagon contract award announcements, newest first) plus the material scope facts: the $7.5M coverage floor, publication on the signing business day, and the service/min_amount filters. The 'recent window / newest first' framing implicitly separates it from the search/top/coverage siblings even without naming them.

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?

The example questions ('what defense contracts were announced today', 'who won a defense contract this week') give clear context for when to reach for this tool, and the FPDS/USAspending comparison signals when this source is preferable (freshness). It stops short of explicit when-not guidance or a direct pointer to dod_awards_search/dod_awards_top for historical or ranked lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.