Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metaculus_top_comments

Fetch normalized Metaculus question rows where recent public comments received high vote scores over the past week.

Instructions

Metaculus top comments feed. Returns normalized Metaculus question rows for the questions whose recent public comments collected the highest vote scores over roughly the last week. Derived from credential-free public Metaculus data; upstream comment bodies are not exposed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return, default 10, max 25
topicNoOptional Metaculus topic slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the data source (public Metaculus data, no credentials) and a key limitation (comment bodies not exposed). However, it lacks details on caching, rate limits, or whether the data is precomputed or live. The time window is noted as 'roughly the last week.'

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is just two sentences: the first defines purpose and scope, the second adds data source and a critical limitation. No wasted words, front-loaded with key information.

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?

The description lacks detail on the output structure (fields of the 'normalized question rows'), which is needed since no output schema is provided. The 'topic' parameter is only mentioned in the schema; the description doesn't explain its effect. Overall, it covers core functionality but is incomplete for a tool without an output schema.

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?

Both parameters (limit, topic) have descriptions in the schema (100% coverage). The description adds no additional meaning beyond what the schema already provides. Baseline score of 3 applies.

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?

The description clearly states it returns 'normalized Metaculus question rows for the questions whose recent public comments collected the highest vote scores over roughly the last week.' It distinguishes itself by specifying it returns question rows (not comments) and that comment bodies are not exposed, setting it apart from sibling tools like metaculus_comments_feed.

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?

The description implies usage for retrieving questions with highly-voted comments over the past week, but it does not explicitly state when to use this tool versus alternatives like metaculus_comments_feed or metaculus_category_questions. No direct comparisons or exclusions are provided.

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