Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

metaculus_category_questions

Fetch Metaculus question rows by category slug to support forecasting research, with an optional limit of up to 25 results.

Instructions

Metaculus category questions. Returns Metaculus question rows for a category. 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

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

C2.9/5.0
Behavior2/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 of behavioral disclosure. It only states that it returns rows and lists allowed slugs; it does not cover read-only safety, pagination, rate limits, or what happens on invalid input.

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

Conciseness3/5

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

The first two sentences are concise and front-loaded, but the third sentence is a long enumeration of category slugs that exactly repeats the schema enum, adding length without new value. The structure is clear but includes redundant content.

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 read tool with no output schema, the description gives basic purpose and valid slug values. However, it omits any description of return structure, pagination behavior, or usage context, leaving gaps that an agent might need when interpreting results.

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 both parameters. The description's list of allowed slugs duplicates the enum without adding new meaning, and it does not mention the limit parameter. Baseline 3 is appropriate when schema does the heavy lifting.

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 states a clear verb ('Returns') and resource ('Metaculus question rows'), and scopes it to a category. It distinguishes itself from some siblings by the 'category questions' framing, but does not explicitly differentiate from related 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 Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives, nor any conditions or exclusions. The intended usage must be inferred from the name and the allowed slugs list.

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