Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metaculus_comments_feed

Track Metaculus questions referenced by recent public comments. Returns question rows in comment-recency order, optionally filtered by topic, without exposing comment bodies.

Instructions

Metaculus comments feed. Returns Metaculus question rows for the questions referenced by the most recent public comments, in comment recency order. 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 burden. It does disclose two useful behavioral facts: results are ordered by comment recency, and comment bodies are deliberately not exposed. It says nothing about permissions/auth, rate limits, or pagination beyond the limit parameter.

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 tight sentences with the key scoping fact (returns questions, not comment bodies) placed where it will be read. The opening 'Metaculus comments feed' is close to a restatement of the name, a minor redundancy, but nothing is bloated.

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?

There is no output schema or annotation coverage, so the description must convey the return. It does the most important part — explaining that question rows (not comments) are returned and how they are ordered. It stops short of describing the row fields, but for a simple two-parameter feed it is largely sufficient.

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%, so limit and topic are already documented in the schema; baseline is 3. The description adds ordering semantics (comment recency) but no extra meaning for the topic slug or the limit behavior beyond what the schema states.

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?

The description names a specific resource and return shape: 'Returns Metaculus question rows for the questions referenced by the most recent public comments, in comment recency order.' This is notably precise — it clarifies that the tool returns questions, not comment bodies, which is the non-obvious thing an agent needs. It does not name a sibling like metaculus_top_comments to differentiate explicitly, keeping it at 4.

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 implied rather than stated: an agent can infer this surfaces questions with recent comment activity. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., metaculus_top_comments) to route between the two comment-oriented siblings.

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