Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

polymarket_dashboard_macro

List Polymarket macro dashboard events with volume, liquidity, and nested markets; use cursor to fetch next pages.

Instructions

List Polymarket macro dashboard events. Lists events from Polymarket's macro dashboard, tagged macro, up to limit events (default 20, max 100). Each event has its title, slug, dates, volume, liquidity, open interest, tags and nested markets with outcomes and prices. Pass the returned cursor back to fetch the next page; has_more shows whether there is one.

Input 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.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and does well: it discloses pagination via the returned `cursor`, the `has_more` signal, and the default/max limit of 20/100. It also enumerates the returned fields (title, slug, dates, volume, liquidity, open interest, tags, nested markets with outcomes/prices). It stops short of noting auth or rate-limit context, but coverage is solid.

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 front-loaded sentences with almost no waste, ordering purpose, then parameters, then pagination. The opening two clauses restate the same idea ('List ... events. Lists events ...'), a minor redundancy that keeps it out of 5 territory.

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, so the description must describe returns, and it does by listing event fields and nested market outcomes/prices plus pagination signals. Together with the fully documented two-parameter schema, an agent has what it needs; only the lack of any alternative-tool routing keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3. The description adds genuine semantics: it explains that `cursor` is fed back from a prior response to fetch the next page and that `limit` defaults to 20 and caps at 100, going beyond the schema's own wording about cursor origin.

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 verb and resource ('List Polymarket macro dashboard events') and scopes it precisely ('tagged `macro`', up to `limit`). An agent can tell it covers macro-category events, though it doesn't explicitly contrast against nearby sibling tools like polymarket_events or polymarket_tag.

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 by 'macro dashboard' and the `macro` tag, so an agent can infer this is for macro-category events. However, there is no explicit when-to-use vs. when-not, and no sibling (e.g. polymarket_events, polymarket_tag) is named as the alternative, leaving routing to inference.

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