govcon-feed

delta_digest

Weekly delta digest for a filter: new awards, modifications, and contracts EXPIRING in the next N days (recompete opportunities). Best signal for BD teams.

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

Input Schema

Name	Required	Description
`days`	No	Lookback days for new/modified (default 7).
`naics`	No
`agency`	No
`keyword`	No
`maxAmount`	No
`minAmount`	No
`recipient`	No
`expiringDays`	No	Expiry horizon, 90 or 180 (default 90).

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 21, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose whether the tool is read-only, destructive, or any side effects. It implies a non-modifying digest but omits response format, authentication needs, or rate limits.

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 description is two sentences, front-loaded with the core purpose. It is concise but could benefit from a brief summary of filtering options or output example.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters and no output schema, the description is insufficient. It does not explain the return format, how filters interact, or provide example usage. The tool is underdocumented for effective selection and invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% (only 'days' and 'expiringDays' have descriptions). The description adds minimal meaning beyond correlating 'expiringDays' with expiring contracts. Key parameters like 'naics', 'agency', 'keyword', 'maxAmount', 'minAmount', and 'recipient' are left entirely unexplained.

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?

The description clearly states the tool provides a weekly delta digest of new awards, modifications, and expiring contracts, with filtering. It distinguishes from sibling tools like 'search_awards' by focusing on time-bound changes and recompete opportunities.

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 description indicates it is 'best signal for BD teams' and implies use for weekly monitoring. It lacks explicit when-not-to-use or comparisons with alternatives, but the purpose is clear enough for situational guidance.

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

All govcon-feed tools Inspect

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

Need Help?