Skip to main content
Glama

Forecast Agencies

forecast_agencies
Read-onlyIdempotent

What procurement-forecast coverage actually exists, which agencies are wired, how many forecast rows each currently publishes, and the honest verdict for every agency on the acquisition.gov forecast index that is NOT wired, with the reason (HTML page with no data file, PDF-only, or blocks automated clients). Call this before concluding that an agency has no upcoming work: an agency absent from the search index has not been checked, which is a different thing from having nothing planned. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "forecast_agencies"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description adds 'Keyless' (no auth needed) plus an important data-completeness caveat about agencies that are HTML-only, PDF-only or block automated clients. That caveat is real value beyond the structured fields. It does not, however, describe the shape or size of the response (list vs. grouped object, ordering, pagination), which matters for a coverage-inventory tool.

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?

Two sentences, roughly seventy words, with the usage trigger placed after the content summary where it is easy to find. The first sentence is a run-on that stacks four deliverables in one clause chain, and 'the honest verdict' is editorial color that could be dropped, but no sentence is filler.

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?

With no parameters and no output schema, the description carries nearly the whole burden and discharges most of it: it enumerates what is reported per wired agency, what is reported for unwired agencies, and why coverage may be missing. The main residual gap is return shape and ordering, which an agent cannot infer from anything else in the definition.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline applies. No parameter-level claims are made or needed.

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 concretely what the call returns: which agencies have forecast coverage wired, how many forecast rows each publishes, and the status plus reason for every agency on the acquisition.gov index that is not wired. It is specific about the resource (procurement forecast agency coverage) and separable from forecast_search/forecast_detail, though it never names those siblings and opens with a noun clause rather than a verb.

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?

It gives an explicit trigger: 'Call this before concluding that an agency has no upcoming work,' with the rationale that an agency absent from the search index has not been checked. That is a clear when-to-use rule tied to a real failure mode. It stops short of naming forecast_search or forecast_detail as the follow-up step once an agency is confirmed wired.

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.