Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get live market activity

get_live_activity
Read-onlyIdempotent

Identifies which Polymarket markets are currently live by condition IDs, returning their market, event and series slugs for quick verification.

Instructions

Which of these markets are live on the site, with their market, event and series slugs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "condition_ids": "<condition_ids>"
    },
    "name": "get_live_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
condition_idsYes

Output Schema

NameRequiredDescriptionDefault
marketsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered elsewhere. The description adds little beyond that: it does not define what 'live' means (open for trading vs. not resolved vs. not closed), does not mention the 50-condition cap or behavior for invalid/unknown condition ids, and does not say whether results are partial or ordered.

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?

A single short sentence with no filler, and the core operation leads. The interrogative fragment style is slightly informal but costs no space; nothing needs to be cut.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but the definition is thin for a batch filter tool: the meaning of 'live', the input identifier semantics, and the batch size limit are all absent. An agent could call it but could easily pass the wrong identifiers or misinterpret an empty result.

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

Parameters2/5

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

Schema description coverage is 0% for the single required parameter, condition_ids. The description only refers to them as 'these markets', which does not explain that the input is a list of condition ids, what format they take, or how they relate to markets/events/series slugs returned.

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 concrete operation on a concrete resource: filter a set of markets down to those that are live, returning market, event and series slugs. That is more specific than the title and distinguishes it from pure lookup tools like get_market, though it gives no explicit sibling differentiation.

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?

The description never says when an agent should call this instead of alternatives such as get_market or get_event_live_volume, nor does it state prerequisites or what to do with non-live results. Only the bare operation is implied by the sentence.

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