Skip to main content
Glama
govconapi

io.github.govconapi/govconapi

Official

Search Forecasts

search_forecasts
Read-onlyIdempotent

Find planned federal procurement forecasts before solicitations are posted. Search pre-solicitation opportunities by agency, NAICS, keywords, value, or recompete status.

Instructions

Search agency procurement forecasts, the only FORWARD-LOOKING layer in this API. These are pre-solicitation: work an agency has planned but hasn't posted an opportunity for yet.

Market Research tool. Use this to find what's coming before it's postable, not what's
live now (for live notices, use search_opportunities instead).

- source: fco | dhs | hhs (which agency forecast feed)
- naics: 2-6 digit code, prefix match (e.g. "5415" matches 541511, 541512...)
- is_recompete: true = only forecasts that name a current incumbent (see below)
- amount_min/amount_max: USD, matched against the forecast's value range
- active_only: default true, excludes already-awarded/cancelled forecasts
- keywords: full-text search over title + description
- sort_by: est_award_fy | est_solicitation_date | value_high | agency | last_updated_date

Recompete signal: when `is_recompete` is true, each row's `incumbent_piid` is the SAME
identifier `get_contract` and `get_vehicle` take as `piid`, chain into either to see who
currently holds it, its value, and when it expires (Pro accounts get this pre-joined
inline as `incumbent_award`, so check that field before making the extra call).
Direct-line PoC contact fields (poc_email, poc_phone, co_email, sb_specialist_email/phone)
are Pro-gated; poc_name stays visible on every plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
naicsNo
stateNo
agencyNo
offsetNo
sourceNo
statusNo
sort_byNo
keywordsNo
set_asideNo
amount_maxNo
amount_minNo
sort_orderNo
active_onlyNo
est_award_fyNo
is_recompeteNo
est_award_quarterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Reveals behavioral details beyond the annotations, such as Pro-gated contact fields, the recompete signal chaining to get_contract/get_vehicle, and the default active_only filter. This adds valuable transparency about data availability and cross-tool integration.

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 well-structured, starting with a clear purpose, then a parameter list with examples, and a separate note on recompete and contact fields. It packs substantial information without redundancy or fluff.

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?

Given that an output schema exists, the description provides sufficient context about return fields (e.g., incumbent_piid, poc_email) and cross-tool usage. It lacks explicit pagination details but includes defaults for limit and offset. Overall, it is fairly complete for a search tool.

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?

Provides meaningful explanations for key parameters (source, naics, is_recompete, amount_min/max, active_only, keywords, sort_by) with concrete examples. However, several parameters (limit, offset, state, agency, status, set_aside, etc.) are not explicitly described, though their names are self-explanatory. Overall, adds value but not exhaustive.

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?

Clearly states the tool's purpose as searching procurement forecasts, explicitly distinguishing them as forward-looking pre-solicitation. Names the alternative tool 'search_opportunities' for live notices, making the scope unambiguous.

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 guidance on when to use this tool versus alternatives, and includes detailed parameter explanations with examples (e.g., NAICS prefix matching, recompete chaining). Directs users to related tools for additional context.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/govconapi/govconapi-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server