Skip to main content
Glama

Dod Contract Announcements

Dod Awards Search

dod_awards_search
Read-onlyIdempotent

Search US Department of War (Pentagon) contract award announcements by contractor name or by keyword in the award description, "has Lockheed Martin won a defense contract", "defense contracts for hypersonic missiles", "Pentagon awards mentioning drone swarms". At least one of query or contractor is required. Optionally restrict to awards announced on or after a given date. This is the leading, weeks-ahead-of-USAspending record of an award; combine with the usaspending pack for the fully structured historical record.

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": {
      "contractor": "Lockheed"
    },
    "name": "dod_awards_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax awards to return (1-100, default 25).
queryNoFree-text match (case-insensitive) against the award description paragraph, e.g. "hypersonic", "F-35 sustainment", "shipbuilding".
sinceNoOnly awards announced on or after this date (YYYY-MM-DD).
contractorNoFree-text match (case-insensitive) against the contractor name, e.g. "Lockheed Martin", "Raytheon".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so safety and idempotency need no restating. The description contributes genuinely useful behavior the annotations cannot: the data is a leading, weeks-ahead-of-USAspending record of an award, so results may later appear in structured form elsewhere. It does not address result ordering, pagination, or rate limits, which keeps it out of the top band.

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 purpose is front-loaded in the first clause, followed by concrete query examples and then the constraints, so an agent can stop reading early and still act. The closing sentence about the USAspending pack is dense but earns its place by setting expectations about result freshness. Minor cost: the inline example list makes the opening sentence long.

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?

There is no output schema, so the description carries the burden of framing what comes back, and it does so indirectly by describing awards as announcement records and pointing to the usaspending pack for structured history. Combined with a fully documented four-parameter schema and complete annotations, an agent has enough to invoke it correctly. It could be slightly more complete by noting whether results are ordered by announcement date or truncated by the limit.

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 per-parameter meanings are already documented, resetting the baseline to 3. The description still adds real semantics the schema does not express: the cross-parameter rule that at least one of query or contractor must be supplied, even though the schema lists an empty required array. The since parameter's effect is also restated as a restriction on announcement date rather than award date, which is meaningful disambiguation.

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?

The description opens with a specific verb+resource: search US Department of War (Pentagon) contract award announcements, matched either by contractor name or by keyword in the award description. The example phrasings ("has Lockheed Martin won a defense contract", "defense contracts for hypersonic missiles") make the retrieval target unmistakable. It stops short of distinguishing itself from its obvious siblings (dod_awards_recent, dod_awards_top, dod_awards_coverage), so it is clear but not fully differentiated.

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 states the selection constraint plainly: at least one of query or contractor is required, plus an optional since-date restriction, and it explains the tool's comparative position as the leading, weeks-ahead-of-USAspending record to be combined with the usaspending pack for structured history. What is missing is explicit when-not guidance or named alternatives among the dod_awards_* siblings, which leaves the agent to infer which companion tool to use.

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.