Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metaculus_category_questions

Fetch normalized Metaculus questions for a chosen category slug, with optional row limit, returning structured JSON data.

Instructions

Metaculus category questions. Returns normalized Metaculus question rows from a credential-free public category feed page. Allowed category slugs: artificial-intelligence, computing-and-math, cryptocurrencies, economy-business, elections, environment-climate, geopolitics, health-pandemics, law, metaculus, natural-sciences, nuclear, politics, social-sciences, space, sports-entertainment, technology.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesMetaculus category slug
limitNoRows to return, default 10, max 25

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / slug / enum
      Added value: +[
+  "artificial-intelligence",
+  "computing-and-math",
+  "cryptocurrencies",
+  "economy-business",
+  "elections",
+  "environment-climate",
+  "geopolitics",
+  "health-pandemics",
+  "law",
+  "metaculus",
+  "natural-sciences",
+  "nuclear",
+  "politics",
+  "social-sciences",
+  "space",
+  "sports-entertainment",
+  "technology"
+]
  2. Addedv1.1.0

TDQS

A3.8/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 burden of behavioral disclosure. It usefully adds that the feed is credential-free, public, and returns normalized rows, but it does not describe pagination, ordering, or the structure of the returned question rows.

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?

The description is front-loaded with the core purpose and is otherwise compact. The long list of allowed slugs is somewhat redundant with the schema enum, but it is still readable and serves as a quick reference.

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?

For a simple two-parameter feed tool, the description provides enough to invoke it: the source, the required slug, and the credential-free nature. However, with no output schema, 'normalized question rows' is vague and leaves the return structure underspecified.

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 baseline is 3. The description lists allowed category slugs, which repeats the enum, and adds no new meaning beyond what the schema already provides for the slug and limit parameters.

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 uses a specific verb and resource: it 'returns normalized Metaculus question rows from a credential-free public category feed page.' The term 'category' clearly distinguishes this from sibling tools like metaculus_questions or metaculus_project_questions.

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

Usage Guidelines4/5

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

The description clearly frames the tool's context: retrieving questions for a specific Metaculus category via a public feed. It does not explicitly name alternatives or exclusion conditions, but the category-scoped scope is evident enough for an agent to select it appropriately.

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