Skip to main content
Glama

Acquisition Forecasts

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Forecast Search

forecast_search
Read-onlyIdempotent

Search US federal agency PROCUREMENT FORECASTS — contracts an agency has published its intention to award in a future fiscal year, months to years before any solicitation exists. Answers "what is DHS planning to buy next year", "upcoming IT services opportunities FY27", "planned acquisitions in my NAICS", "future set-aside work for small business". Each result carries the requirement title and description, NAICS, estimated value band, small-business set-aside, anticipated award quarter, contracting office and a named point of contact. This is the DEMAND side and it is forward-looking: for contracts already awarded use USASpending, and for solicitations already open for bid use the govcon tools. Currently covers the Department of Homeland Security and its components (CBP, ICE, TSA, FEMA, USCG, USCIS, USSS, CISA, FLETC) — call forecast_agencies for exactly what is wired and why. Keyless.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax rows, 1–100 (default 20). `total_matches` reports the full count regardless.
naicsNoNAICS code, matched as a PREFIX so "5415" covers 541511/541512/etc. Also accepts a full 6-digit code.
agencyNoAgency key, e.g. "DHS". Omit for all wired agencies. See forecast_agencies.
keywordNoFree text matched against the requirement title and description, e.g. "cloud", "training", "body armor", "case management".
min_valueNoMinimum estimated value in USD, compared against the TOP of each band so a "$10M to $20M" row matches min_value 15000000.
set_asideNoSmall-business program: "8(a)", "SB", "SDVOSB", "HUBZone", "WOSB", "AbilityOne", "None", "TBD".
sub_agencyNoDHS component or office, matched as a prefix of the organization path, e.g. "CBP", "TSA/OIT", "USCG".
fiscal_yearNoFederal fiscal year of the planned award, e.g. 2027.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare the read-only, idempotent, open-world safety profile, but the description adds valuable context beyond them: it discloses scope coverage (DHS and components only), explains what each result contains, and notes the keyless requirement. It stops short of describing pagination 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?

Front-loads the core purpose and is dense with useful routing and scope info, but the description is long and somewhat list-heavy. Each sentence earns its place, though the example-question enumeration could be trimmed.

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?

Covers the critical agent needs: scope, result fields, alternatives, and coverage limitations. With no output schema, it must explain returns, which it does. Could say more about empty-result behavior or pagination, but the definition is functionally complete.

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 parameters are already fully documented (prefix matching for NAICS, band-top comparison for min_value, enum set-aside values). The description adds no parameter syntax beyond what the schema carries, which is the baseline-3 case when the schema does the heavy lifting.

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+resource ('Search US federal agency PROCUREMENT FORECASTS') and defines what a forecast is in a way that separates it from awarded contracts and open solicitations. Explicitly names sibling tools (USASpending, govcon tools, forecast_agencies) as the alternatives.

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

Usage Guidelines5/5

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

Provides explicit when-to-use via example queries ('what is DHS planning to buy next year'), and explicit when-not-to-use by routing awarded contracts to USASpending and open solicitations to govcon tools. Coverage limits (DHS only) are disclosed with a pointer to forecast_agencies.

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

All Acquisition Forecasts toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources