Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_dashboard_macro

List Polymarket macro dashboard events as normalized macroeconomic rows via credential-free Gamma keyset JSON, using limit and cursor pagination.

Instructions

List Polymarket macro dashboard events. Returns normalized macroeconomic event rows for Polymarket's /dashboards/macro page using credential-free Gamma events/keyset JSON with the macro tag.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum macro events, defaults to 20 and supports up to 100
cursorNoOptional keyset cursor from a prior macro dashboard response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A3.9/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 discloses credential-free access, the API endpoint, and the 'macro' tag, but lacks details on pagination behavior, rate limits, return format, or error handling. The mention of 'keyset cursor' implies pagination but is not explained.

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?

Two sentences: the first clearly states the purpose, the second adds technical context. No extraneous information. Front-loaded and efficient.

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?

There is no output schema, so the description should compensate. It mentions 'normalized macroeconomic event rows' but does not specify fields, data types, or pagination structure. For a list tool, more detail on expected output is needed for full completeness.

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?

The input schema already provides descriptions for both 'cursor' and 'limit' (100% coverage). The description adds that the tool uses a specific API endpoint and tag, but does not elaborate on parameter usage beyond what the schema states. Baseline 3 is appropriate.

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 'List' and clearly identifies the resource 'Polymarket macro dashboard events'. It distinguishes this tool from siblings like 'polymarket_events' by specifying that it returns macro dashboard events from a particular page.

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 implicitly indicates when to use this tool (when macro dashboard events are needed) by naming the specific page and tag. However, it does not explicitly state when not to use it or list alternatives among the many sibling tools.

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