Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metaculus_top_comments

Fetch Metaculus question rows ranked by recent public comment vote scores from the past week; optionally filter by topic and limit to surface active debates.

Instructions

Metaculus top comments feed. Returns Metaculus question rows for the questions whose recent public comments collected the highest vote scores over roughly the last week. Comment bodies are not exposed.

Input 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.5/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 behavioral burden. It usefully discloses that comment bodies are NOT exposed and that the window is ~one week ranked by vote score, which prevents misuse. It says nothing about result ordering guarantees, pagination, or auth, leaving meaningful gaps for a feed tool.

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?

Three short sentences, front-loaded with what is returned and immediately followed by the selection criterion and the exposure caveat. The opening 'Metaculus top comments feed' slightly restates the name, but nothing else is wasted.

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 simple two-parameter read feed with no output schema or annotations, the description covers what is returned, how it is ranked, the time window, and the notable exclusion of comment bodies. It is close to complete, missing only ordering/pagination expectations.

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% for both parameters (limit with default/max, topic slug), so the schema already documents them fully. The description adds no extra meaning about how topic scoping interacts with the vote-score ranking, 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?

States a specific output ('Metaculus question rows') and a specific selection criterion ('highest vote scores over roughly the last week'), which resolves the mismatch between the name 'top_comments' and the fact that it returns questions, not comments. It does not explicitly name the neighbouring metaculus_comments_feed, so sibling differentiation is left implicit.

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 'top comments over the last week' framing implies the use case (surface questions with the most active/upvoted discussion), but there is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as metaculus_comments_feed or metaculus_questions.

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