govcon-feed

competitor_watch

Given a contractor name, return their recent federal awards (last 180d live) plus any win/lose/modify events the feed has accrued over time.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contractor": "<contractor>"
    },
    "name": "competitor_watch"
  }
}

Input Schema

Name	Required	Description	Default
`contractor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 21, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description fully carries the burden due to no annotations. It explicitly states the data recency (last 180 days), types of events returned (win/lose/modify), and that events accrue over time. This is good transparency, though it omits potential limitations like pagination or number of results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, well-structured sentence that conveys all necessary information without extraneous words. It is front-loaded and efficient.

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 tool with one parameter and no output schema, the description covers the main functionality and data scope (180 days, events). It does not describe the return structure, but the context is sufficient for an agent to understand the tool's purpose and when to use it.

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 single parameter 'contractor' is described as 'contractor name' in the description, adding context beyond the bare string type in the schema. However, it does not specify expected format (e.g., exact name, partial match), which could leave ambiguity.

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 takes a contractor name and returns recent federal awards and win/lose/modify events. It specifies the time window (last 180 days) and event types, distinguishing it from sibling tools like search_awards (general search) and delta_digest (diffs).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly suggests use for monitoring a specific contractor's activity, but it lacks explicit guidance on when to use this tool versus alternatives (e.g., search_awards for broader queries). No when-not-to-use or exclusion criteria are provided.

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?