Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metaculus_question_forecasts

Return current Metaculus question forecasts by id, grouped by aggregation method, including forecaster counts, center, lower/upper ranges, and question details.

Instructions

Metaculus question forecasts. Returns the latest forecast summary per aggregation method for one Metaculus question, by numeric id. Each method has its name, forecaster count, center, lower and upper values, and number of history points. recency_weighted, unweighted and single_aggregation are listed first when present. The question details come with it.

Input Schema

NameRequiredDescriptionDefault
idYesMetaculus question or post id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the disclosure burden and does so reasonably: it lists the returned fields (name, forecaster count, center, lower/upper values, history points), and specifies that recency_weighted/unweighted/single_aggregation are ordered first when present. It omits any auth or rate-limit context, but implies a safe read via 'Returns'.

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?

Short and front-loaded, with purpose first and return-shape detail following. Every sentence roughly earns its place, though the aggregation-ordering note is fairly granular for a one-parameter tool.

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?

For a single-parameter read with no output schema, the description supplies enough about the response shape (fields and method ordering) for an agent to call and interpret it. It stops short of full completeness by not touching error behavior or identifier acquisition, but nothing essential is missing.

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% (the schema documents 'Metaculus question or post id'). The description adds only the detail that the id is numeric, a marginal clarification over the schema. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a precise verb and resource ('Returns the latest forecast summary per aggregation method for one Metaculus question') and scopes it to a single question by id. The 'latest ... per aggregation method' phrasing cleanly distinguishes it from the sibling metaculus_question_forecast_history, which implies a time series.

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: 'latest forecast summary' hints at the contrast with forecast_history, but no sibling is named and no when-to-use vs when-not guidance is given. An agent can infer the appropriate context but must do the work itself.

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

Deploy Server

Other Tools