Skip to main content
Glama
PaulieB14

graph-polymarket-mcp

by PaulieB14

get_recent_activity

Retrieve recent splits, merges, and redemptions from Polymarket's Activity subgraph. Optionally filter by Ethereum address to track specific trader actions.

Instructions

Get recent splits, merges, and redemptions from the Activity subgraph

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
firstNoNumber of events to return
accountNoOptional: filter by Ethereum address
Behavior2/5

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

No annotations and minimal behavioral detail. 'Recent' is undefined; no mention of ordering, pagination, rate limits, or possible empty results.

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?

Single sentence, clear and focused. Slightly penalized for lack of structure (e.g., no headings or bullet points), but still efficient.

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?

No output schema and no annotations; description fails to explain what is returned or how results are ordered. Lacks essential context for a tool with optional parameters.

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 coverage is 100% with descriptions for both parameters. The tool description adds no additional meaning beyond the schema, so baseline score of 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 clearly states it retrieves recent splits, merges, and redemptions from the Activity subgraph, using specific verbs and resources. It distinguishes from sibling tools that focus on markets, stats, or trader profiles.

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 guidance on when to use this tool versus alternatives like get_market_data or get_trader_profile. Lacks explicit context for selection.

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/PaulieB14/graph-polymarket-mcp'

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