Skip to main content
Glama

due_forecasts

List register forecasts whose due date falls within the given number of days (including those already due and still open). Futures essays are not included. Signetex grades evidence and issues no true/false verdicts.

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

Input Schema

NameRequiredDescriptionDefault
within_daysNoInclude forecasts due on or before today plus this many days (default 365, max 3650). Already-due open forecasts are included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: already-due open forecasts are included, futures essays are excluded, and defaults/limits are implied. It is silent on ordering, pagination, result volume, and required access, which matter for a listing tool with no output schema.

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 core scope is front-loaded in one efficient sentence, and the futures-essay exclusion is a useful qualifier. The closing sentence about Signetex grading evidence and issuing no verdicts is tangential to a due-date listing and doesn't earn its place as strongly as the rest.

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 single-parameter read tool this is mostly adequate, and the schema plus annotations-free simplicity lower the bar. Still, with no output schema the description never indicates what a returned forecast entry looks like or how results are ordered, which an agent would want before calling.

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 coverage is 100% and the single optional parameter already documents the default of 365, the 3650 maximum, and inclusion of already-due items. The description restates the same range semantics rather than adding new meaning, 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 specific verb and resource ('List register forecasts') plus the exact filter (due date within N days), so the agent knows precisely what comes back. It does not name a sibling tool or contrast itself with search_claims or evidence_grades, which keeps it short of a 5.

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

Usage Guidelines3/5

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

Usage is implied by the filter ('forecasts due within the given number of days'), and the exclusion of futures essays sets a boundary. However, there is no explicit when-to-use/when-not-to-use framing and no alternative named for retrieving forecasts by other criteria, leaving the agent to infer routing.

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