Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metaculus_question

Fetch a single Metaculus question by numeric ID and return its title, status, timing, forecasts, categories, and URL.

Instructions

Metaculus question detail. Returns one Metaculus question by numeric id (a question or post id). The response has the title, status, question type, unit, open, close and resolve times, forecaster and forecast counts, comment count, latest forecast center and bounds, categories, projects and URL.

Input Schema

NameRequiredDescriptionDefault
idYesMetaculus question or post id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It helpfully enumerates the response fields (status, counts, forecast center, etc.) and implies a read operation via 'Returns'. But it never states explicitly that this is read-only/side-effect-free, nor any auth or rate-limit behavior.

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, no filler, and the return-content detail is front-loaded right after the core purpose. Efficient for a simple lookup 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?

With no output schema, the description substitutes by enumerating the returned fields, which is genuinely useful. For a single-parameter read tool with no annotations, this covers the essentials; only the safety profile and sibling differentiation are unaddressed.

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 the schema already documents the single 'id' parameter. The description adds only that the id may be a question or post id, which the schema already states, plus a 'numeric' hint that is slightly at odds with the string type. 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?

States a specific verb and resource: 'Returns one Metaculus question by numeric id.' The agent knows exactly what it fetches. However, it does not differentiate from siblings like metaculus_question_metadata, metaculus_question_options, or metaculus_question_forecasts, which also operate on question ids.

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

Usage Guidelines2/5

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

No explicit when-to-use or when-not-to-use guidance. Given a dense cluster of sibling tools (metaculus_question_metadata, metaculus_question_options, metaculus_question_forecasts, metaculus_question_forecast_history), the description gives no routing signal to help pick this over them.

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