Skip to main content
Glama

AEGIS (McX Ventures)

Defense-stock signal: Pentagon contract awards by ticker

dow_awards
Read-only

Defense-stock event signal: U.S. Department of War contract awards ($7.5M+) from the official 5 PM ET daily announcements, normally published the same evening, matched to public tickers and sized as % of the company's annual revenue (material / notable / routine), with action vs ceiling vs obligated dollars, new vs existing work and corrections. Each day's dataset hash is anchored on Base. Feed freshness is reported in every response and free at /dow-awards/index Price: $0.01 USDC on Base per call, paid with x402.

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": "dow_awards"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOne announcement day, YYYY-MM-DD. Omit all dates for the latest day.
limitNo
tickerNoOnly awards whose awardee maps to this ticker, e.g. LMT.
date_toNoRange end, YYYY-MM-DD.
min_tierNoMinimum materiality tier (award vs annual revenue).
date_fromNoRange start, YYYY-MM-DD (range max 31 days).
exclude_existingNoDrop option exercises / modifications.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly/openWorld; the description adds substantial context beyond them — publication timing (5 PM ET, normally same evening), the $7.5M+ default threshold, per-call pricing of $0.01 USDC via x402, per-day hash anchored on Base, and freshness reporting in every response. Cost/payment and provenance are exactly the traits an agent needs before invoking.

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 purpose and dense with useful facts, with no true filler. The trailing pricing/endpoint sentences are justified but make the block long and slightly sales-flavored; a small trim would improve scanability.

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 7-parameter, no-output-schema tool, it covers what the response contains (dollar breakdown, tier, new vs existing, corrections, freshness) and the invocation cost. Remaining gaps like limit defaults and awards without a matching ticker are minor.

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 already 86%, so baseline is 3; the description adds real meaning by defining the materiality tiers as award-vs-annual-revenue and disclosing the implicit $7.5M+ floor that no parameter expresses. It also clarifies the domain concepts (action vs ceiling vs obligated, new vs existing work) that underpin min_tier and exclude_existing, though it doesn't explain limit/pagination behavior.

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?

Names a specific resource (U.S. DoW contract awards from the official 5 PM ET daily announcements) plus the derived signal layer (ticker-matched, sized as % of annual revenue, tiered). An agent immediately knows this returns defense-contract event data, clearly distinct from the DNS/TLS/CT/forensics 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?

Establishes clear context: use it for defense-stock event signals, omit all dates for the latest day, and points to the free /dow-awards/index for freshness checks. It stops short of explicit when-not guidance or naming an alternative tool for related needs.

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.

Resources