Skip to main content
Glama
DanielTomaro13

sportsdata-mcp

polymarket_events

Retrieve event catalogues with nested markets. Filter by active, closed, slug, tag, date range, volume, or liquidity to compare odds and trading activity across sports events.

Instructions

Event catalogue (an event groups related markets, e.g. one game or election) with nested markets.

Returns: [{id, title, slug, description, volume, liquidity, endDate, tags, markets:[{id, question, clobTokenIds, outcomePrices}]}] (top-level array)

Example: Most-traded active events

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNo
limitNo
orderNo
activeNo
closedNo
offsetNo
tag_idNo
archivedNo
ascendingNo
series_idNo
volume_minNo
end_date_maxNo
end_date_minNo
liquidity_minNo
Behavior3/5

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

With no annotations, the description provides the return format and an example, which gives some transparency about the output structure. However, it lacks information on authentication, rate limits, empty results, pagination behavior (though offset is in schema), or other behavioral traits. The output structure is well-defined, but not enough for full transparency.

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 concise: two sentences plus a return format block. It is front-loaded with purpose and an example. The return format is detailed but could be more structured (e.g., bullet points). No unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 14 parameters, no schema descriptions, no output schema, no annotations, and many sibling tools, the description is highly incomplete. It does not explain how to use parameters, what each filter does, or how to retrieve specific types of events. The example is vague and insufficient for proper tool use.

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

Parameters1/5

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

Schema description coverage is 0% (no parameter descriptions in schema), and the description adds no meaning for any of the 14 parameters. It does not mention filters like 'active', 'closed', 'slug', 'tag_id', etc. This is a critical gap.

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 clearly states it returns an event catalogue with nested markets, and provides an example 'Most-traded active events'. The verb 'returns' and the structured output make the purpose clear. It distinguishes from singular 'polymarket_event' by being a listing tool, though it does not explicitly differentiate from other listing tools like 'polymarket_search'.

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?

No explicit guidance on when to use this tool vs alternatives such as 'polymarket_event', 'polymarket_markets', or 'polymarket_search'. The description implies it is for listing events, but does not state exclusions or provide context on choosing among sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DanielTomaro13/sportsdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server