Stop receiving real-time data updates from Polymarket by removing an active subscription ID. Cancels ongoing feed notifications immediately.
Unsubscribe from a real-time data feed. Removes a subscription by ID (obtained from subscribe_* tools). Stops receiving updates for that subscription.
| Name | Required | Description | Default |
|---|---|---|---|
| subscription_id | Yes | Subscription ID to remove |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the primary effect (stops receiving updates) but does not mention idempotency, invalid-ID handling, or whether the effect is immediate. Adequate for a simple tool, but lacking edge-case behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, each carrying useful information. The action is front-loaded, and no filler or redundant phrasing is present.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-parameter tool with no output schema, the description covers the essential facts: what it does, how to identify the subscription, and the resulting behavior. Minor omissions around error/resubscription semantics are acceptable given the tool's simplicity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% ('Subscription ID to remove'). The description adds value by clarifying that the ID must come from subscribe_* tools, establishing a valid source and narrowing the accepted value beyond the plain schema text.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific action ('Unsubscribe'), the resource ('real-time data feed'), and the mechanism ('Removes a subscription by ID'). It is unambiguous and clearly distinguishes this from the subscribe_* and market query sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Indicates the tool should be used when a subscription ID from subscribe_* tools is available and updates should stop. There are no alternative unsubscribe tools, so explicit exclusions are unnecessary; the source-of-ID note provides practical guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.