Skip to main content
Glama

GW8 Signal API

by io.github.GrayWolf8-creator
OverviewDiscussionsAdmin

Federal contract feed

get_gov_contracts

Recent (14-day) US federal contract actions to AI, drone, nuclear, robotics, space, quantum and defense-tech companies (USAspending.gov), with tickers, amount, agency, date, description, award link. Optional ticker / sector / q filters. NOTE: the Department of War daily announcements source is currently blocked from our host (sourceStatus.dodAnnouncements=unavailable; check free GET /api/govcontracts/status), so DoD awards currently appear only via USAspending with a ~90-day lag. Paid: $0.01 USDC on Base, paid in-band via x402 MCP (@x402/mcp; _meta "x402/payment"). Also at GET https://micro-saas-agent.onrender.com/api/govcontracts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
passNoOptional GW8 day pass token (from buy_day_pass / POST /api/pass/day); skips per-call payment
sectorNo
tickerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pass
      Added value: +{
+  "description": "Optional GW8 day pass token (from buy_day_pass / POST /api/pass/day); skips per-call payment",
+  "maxLength": 80,
+  "type": "string"
+}
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: data source and 14-day window, an explicit blocked-source disclosure (dodAnnouncements=unavailable) with a ~90-day DoD lag, and the payment requirement ($0.01 USDC on Base via x402, or a pass token). These are exactly the behavioral 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-loads the resource and scope, then filters, then the source caveat and payment note. Dense but mostly earning its place; the trailing RAW URL is arguably redundant with the tool binding itself.

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?

No output schema exists, yet the description enumerates returned fields, states the payment/auth path, and flags the data-freshness limitation. For a 4-param, zero-required read feed, nothing an agent needs to call it correctly is missing.

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 only 25% (only 'pass' documented), so the description should compensate. It labels the filters as optional but adds no semantics beyond the schema: what 'q' matches, what each sector enum value denotes, or the ticker format (only a pattern in the schema). Marginal value over structured fields.

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 ('Recent (14-day) US federal contract actions') with precise coverage: sector list, source (USAspending.gov), and returned fields (tickers, amount, agency, date, description, award link). No sibling overlaps in the feed line, so the agent can distinguish it immediately.

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?

Names the optional filters (ticker / sector / q) and gives context for the DoD source gap plus a status-check endpoint. However, it does not explicitly say when to prefer this feed over a sibling or what would steer an agent elsewhere; guidance is clear but not exclusionary.

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

All GW8 Signal API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources