unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id (uuid) returned by subscribe. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations provide readOnlyHint, destructiveHint, and idempotentHint. The description adds ownership enforcement, clarifies deactivation vs. deletion, and notes that historical events remain available. No contradiction with annotations.
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 sentences with no wasted words. Each sentence conveys essential information: the action, constraints, and side effects.
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?
The description is adequate for a simple mutation with one parameter and no output schema. It covers ownership, side effects, and relationship to another tool. However, it could mention idempotency explicitly, though annotations cover it.
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%, and the schema already describes 'id' as 'Subscription id (uuid) returned by subscribe.' The tool description does not add significant meaning beyond that, meeting the baseline of 3.
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?
The description clearly states 'Cancel a subscription by id,' which is a specific verb and resource. It distinguishes from siblings like 'subscribe' and 'list_subscriptions' by clarifying the deactivation behavior and linking to 'recent_alerts' for historical events.
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?
The description includes ownership enforcement ('you can only cancel your own subscriptions') and explains that deactivation keeps historical events accessible via 'recent_alerts.' It implicitly guides when to use the tool but lacks explicit when-not or alternative distinctions for a perfect score.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools overlap significantly in purpose, especially the ask_pipeworx variants (standard, beta, grounded) and deep_research, as well as the polymarket arbitrage/edges/fill_risk/kalshi_spread suite. It would be hard for an agent to reliably choose the correct tool without deep understanding of subtle distinctions.
Tool names mostly use snake_case, but there is no consistent prefix or verb pattern. Some names are descriptive phrases (e.g., scream_void_scream, compare_entities) while others are vague (e.g., forget, recall). The mix of 'pipeworx_' prefix on some tools and lack of it on others adds inconsistency.
32 tools is on the high side for a data research server, given the overlapping functionality. Some tools could be merged (e.g., the ask_pipeworx variants, polymarket tools). However, the count is not excessive enough to be unmanageable, and each tool serves a specific niche.
The server covers a broad range of data sources and prediction market analysis, with tools for research, comparison, monitoring, and memory. Minor gaps exist (e.g., no tool to update stored memories or manage subscriptions beyond CRUD), but core workflows are well-supported.