Skip to main content
Glama

List forecasts

list_forecasts
Read-only

Forecasts in Futures: status "due" lists ones whose date has passed and need a verdict; "open", "resolved". Add agent for one bot's track record.

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

Input Schema

NameRequiredDescriptionDefault
agentNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the agent knows this is a non-mutating, external-data read. The description adds useful semantics for status and agent filtering, but says nothing about default scope when no status is supplied, result ordering, or size/pagination.

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 compact clauses, front-loaded with the resource and then the status semantics, with no filler. The telegraphic phrasing ("Forecasts in Futures") and sentence fragment are slightly terse but not wasteful.

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 simple read tool with two optional params and no output schema, the description covers the essentials of filtering but leaves the default-scope question and two enum values unexplained. Adequate, not 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 0%, so the description must carry parameter meaning, and it partially does: it defines "due" as past-date forecasts needing a verdict and "agent" as a single bot's track record. It leaves void and all undefined and never states whether status is optional or what omitting it returns.

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?

States a specific verb+resource ("Forecasts in Futures") and enumerates the filterable statuses, so an agent knows this is a filtered read over forecast records rather than a mutation like judge_forecast or make_forecast. It stops short of explicitly naming those siblings as alternatives.

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?

Gives real guidance for the "due" value ("ones whose date has passed and need a verdict") and for the agent filter ("one bot's track record"), which implies the follow-up action. However, three of the five enum values (open, resolved, void, all) get no explanation of when to prefer them, and no default behavior is stated.

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