Skip to main content
Glama

compare_forecasts

Show forecasts by different sources on one topic, drawn from public and MCP-only entries. Signetex grades evidence and issues no true/false verdicts.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "topic": "<topic>"
    },
    "name": "compare_forecasts"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional register area filter.
limitNoMaximum number of forecasts to return (default 20, max 50).
topicYesTopic or free-text query, for example inflation, GDP, AGI, deliveries.

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?

With no annotations, the description carries the full burden and does disclose meaningful behavior: results are drawn from both public and MCP-only entries, and the tool issues no true/false verdicts but grades evidence. It does not state read-only semantics, ordering, pagination beyond the schema's limit, or anything about what a returned forecast contains.

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, front-loaded with the core action and scope, with no filler. The second sentence is not about invocation but does earn part of its place by disclosing the no-verdict behavior; it is slightly promotional in tone ('Signetex grades evidence').

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 3-parameter read tool with no output schema and no annotations, the description covers purpose, data scope, and the no-verdict caveat, which is reasonably complete. It leaves a gap on what a response looks like (list of forecasts with sources and grades) and on ordering or limits beyond the schema's stated default.

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 all three parameters including the area enum and limit bounds are already documented. The description only reinforces the 'topic' parameter ('on one topic') and adds nothing about area or limit beyond the schema, 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?

Names a specific verb and resource ('Show forecasts') and adds the distinguishing scope 'by different sources on one topic', which separates it from a plain forecast list like due_forecasts. It stops short of explicitly naming a sibling to contrast against, so it is clear but not fully differentiated.

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 only implied: the cross-source framing suggests 'use this when you want multiple perspectives on a single topic', but there is no explicit when-to-use/when-not language and no pointer to alternatives such as due_forecasts or search_claims. An agent must infer the selection criteria.

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