Skip to main content
Glama

Track recompetes

track_recompete
Read-onlyIdempotent

Not affiliated with the U.S. government, GSA, or SAM.gov. Not a U.S. government service. Find contracts nearing end of performance and likely recompete candidates. Dates are estimates from recorded periods of performance. Not a prediction that a solicitation will happen. Present as information only. Follow-ups within 30 minutes after a search ride free (up to 30 per search); otherwise one accepted call counts as one use.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum 25 records; minimum 1; default 10.
naicsNoNAICS codes to scan for recompetes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum 25 records; minimum 1; default 10."
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, destructiveHint=false), and the description adds genuinely new context beyond them: results are estimates derived from recorded periods of performance and must be presented as information only, not a forecast. It also discloses billing/usage behavior that annotations do not capture — follow-up calls within 30 minutes of a search ride free up to 30 per search, otherwise one accepted call counts as one use.

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

Conciseness3/5

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

Two full sentences of non-affiliation disclaimer precede any statement of what the tool does, so the purpose is buried rather than front-loaded. The remaining sentences are efficient, but the disclaimer block consumes a large share of the text without helping tool selection.

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

Completeness3/5

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

For a simple two-parameter read-only tool, the description covers purpose, data reliability caveats, and quota behavior. It stops short of describing what a returned recompete record looks like (there is no output schema to compensate) and never resolves which of the several recompete-related siblings an agent should choose.

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 description coverage is 100%, so both `limit` (1–25, default 10) and `naics` (2–6 digit code pattern) are fully documented in the schema itself. The description adds no extra meaning about how NAICS filtering is applied or how the limit interacts with paging, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete verb and resource: "Find contracts nearing end of performance and likely recompete candidates." That is clear enough for an agent to grasp what the tool returns. It does not, however, distinguish it from near-identical siblings such as find_likely_recompetes, get_recompete_calendar, or list_awards_by_period_end, which all overlap with this purpose.

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

Usage Guidelines2/5

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

Nothing in the text explains when to pick this tool over find_likely_recompetes or the calendar/detail variants, and no prerequisites or exclusions are given. The only guidance present is interpretive ("dates are estimates," "not a prediction that a solicitation will happen"), which tells the agent how to read output, not when to invoke the tool.

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