Skip to main content
Glama

Dod Contract Announcements

Dod Awards Top

dod_awards_top
Read-onlyIdempotent

Ranks contractors or military services/agencies by total defense contract award value over a recent window, "who are the top defense contractors this month", "which service branch awarded the most this quarter". Ranks by money actually obligated. Two kinds of award are held out of that total and reported alongside it, because folding either one in yields a large, plausible-looking number that means nothing: shared_award rows (a multiple-award paragraph whose amount is the COMBINED program value across every winner, not one company's share) and ceiling/not-to-exceed awards (a lifetime maximum on a multi-year contract, not money awarded in this window).

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": {
      "by": "contractor",
      "days": 30
    },
    "name": "dod_awards_top"
  }
}

Input Schema

NameRequiredDescriptionDefault
byNoRank by "contractor" (default) or "service".
daysNoWindow size in days, ending today (default 30).
limitNoMax ranked entries to return (1-100, default 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, but the description goes well beyond them by disclosing the ranking methodology: totals reflect money actually obligated, and shared_award rows and ceiling/not-to-exceed awards are excluded from the rank and reported alongside instead. It even explains why the exclusion matters (combined program value across all winners; lifetime maximum), which is exactly the kind of non-obvious semantic an agent would otherwise misreport.

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 core action and example queries are front-loaded, and each sentence adds information rather than restating the title. The final sentence is dense and clause-heavy, but the caveat it conveys is genuinely load-bearing rather than filler.

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 zero-required-parameter, annotated read tool with an exhaustively documented schema and no output schema, the definition covers purpose, ranking semantics, and the caveat categories returned alongside. Only the shape of the returned ranked entries and the meaning of the companion figures remain unstated, which is a modest gap given no output schema exists.

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 coverage is 100%, with all three parameters documented including the "contractor"/"service" values and the 1-100 limit range, so the schema carries the parameter burden. The description adds only tangential meaning ("over a recent window" for days) and says nothing about how `by` changes the returned ranking. Baseline 3 applies.

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: "Ranks contractors or military services/agencies by total defense contract award value over a recent window," backed by two concrete query examples. The purpose is unambiguous, but the description never contrasts itself with the sibling award tools (dod_awards_search, dod_awards_recent, dod_awards_coverage), so an agent must infer the boundary from the word "ranks" alone.

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 exemplar questions ("who are the top defense contractors this month", "which service branch awarded the most this quarter") make the intended use case clear and easy to pattern-match against a user request. There is no explicit when-not-to-use clause or named alternative, so routing between this and the other dod_awards_* tools is left to inference.

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.