Skip to main content
Glama

FedTally — US Federal Contract Intelligence

Get expiring contracts

get_expiring_contracts
Read-only

Federal contracts whose period of performance ends inside a chosen window for one NAICS industry — the recompete pipeline, useful for finding work about to be rebid and identifying the incumbent to displace. Rows come back soonest expiry first with the end date, days remaining, contract PIID and parent IDV, incumbent vendor name and UEI, contracting department, obligated dollars, total contract value including options, place of performance, and description. Two fields matter most to small contractors: setAside, the socioeconomic set-aside the work was competed under (SDVOSBC service-disabled veteran-owned, WOSB women-owned, 8AN 8(a) sole source, SBA total small business, HZC HUBZone), which is null when the work was competed full and open; and isSmallBusiness, the contracting officer's size determination for the incumbent — together they show whether a small firm is eligible to bid and whether the incumbent is a small business or a large one. Rows are served from nightly SAM.gov snapshots. Coverage is partial and rotating: the sync refreshes the stalest few of the 20 seeded industries each night, so only some are readable at any moment and the set grows over a few nights. The syncedAt field gives the timestamp of the sync that produced the rows, and an industry with no snapshot yet returns a short notice naming the codes that are currently synced, instead of data. Source: SAM.gov Contract Awards v1, public domain US Government data. Vendor street addresses are never returned.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoDays ahead to look for expiring periods of performance. Defaults to 180.
naicsYesNAICS industry code, 2 to 6 digits, e.g. "541511" for custom computer programming.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses nightly SAM.gov snapshots, partial rotating sync coverage, handling for unsynced industries (returning notice), and that vendor street addresses are never returned. This provides rich behavioral context without contradicting annotations.

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 long but front-loaded with its core purpose, then details return fields and sync behavior. Every sentence adds operational value, though it could be considered wordy. It earns its length due to the tool's complexity.

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?

With no output schema, the description compensates by enumerating key return fields, explaining the significance of setAside and isSmallBusiness, and covering the partial sync edge case. This makes it complete for understanding results and limitations.

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?

The input schema already fully documents both parameters (naics with pattern and example, days with default). The description does not add additional meaning about the parameters themselves, focusing instead on output fields. With 100% schema coverage, a baseline score of 3 is appropriate.

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?

Description clearly states it returns Federal contracts expiring within a chosen window for a specific NAICS industry, with a distinct purpose as a 'recompete pipeline.' This is specific and distinguishes it from sibling tools like get_agency_spend and search_awards_by_company without needing to name them.

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 explicitly states it is 'useful for finding work about to be rebid and identifying the incumbent to displace,' giving a clear use context. It does not mention when not to use it or alternative tools, but the use case is unambiguous.

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