Skip to main content
Glama

Dod Contract Announcements

Dod Awards Coverage

dod_awards_coverage
Read-onlyIdempotent

Reports what DoD/Pentagon contract announcement data is currently available: total row count, the earliest and latest announcement date on file, and a per-service breakdown of counts. Use to gauge coverage before relying on it for a historical range, "how far back does Pipeworx's Pentagon contract data go".

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": {},
    "name": "dod_awards_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile needs no restating. The description adds substance the annotations cannot: it discloses exactly what fields come back, which matters because there is no output schema. It does not mention cost, latency, or whether counts reflect partial/live ingestion.

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?

Front-loaded with the payload contents, followed by a single usage sentence; both earn their place. The trailing quoted example phrase ("how far back does Pipeworx's Pentagon contract data go") is slightly redundant filler but does reinforce intent cheaply.

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?

With zero params, no output schema, and annotations covering safety, the remaining burden is describing returns and role — both are covered. An agent has everything needed to decide to call it and to interpret the three reported facts.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly does not invent inputs, implying the call is argument-free.

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 specific verb and resource: reports available DoD/Pentagon contract announcement data, and enumerates the exact payload (total row count, earliest/latest announcement date, per-service breakdown). This makes clear it is a metadata/coverage probe rather than a data-retrieval call, which implicitly separates it from the dod_awards_search/recent/top siblings.

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?

Gives an explicit when-to-use: gauge coverage before relying on the dataset for a historical range, framed as a pre-flight check. It stops short of naming an alternative sibling or stating when this tool should be skipped, so it falls just below the full when/when-not/alternatives bar.

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.