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?
Discloses that the row is deactivated (not deleted) and historical events remain via recent_alerts. Adds context beyond annotations which only hint at non-destructive modification.
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, front-loaded, no wasted words. Every sentence adds value.
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?
Simple tool with one parameter and full annotations; description covers ownership, behavioral effect, and historical data retention sufficiently.
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%; description does not add extra meaning beyond the schema's parameter description. Baseline 3 is appropriate.
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?
Clearly states the action (cancel) and resource (subscription by id). Distinguishes from siblings like subscribe and list_subscriptions.
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?
States ownership enforcement: only cancel own subscriptions. Provides clear usage context but does not explicitly mention when not to use or name alternatives.
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 have overlapping purposes, such as multiple data query tools (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and several prediction market analysis tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.). While descriptions attempt to differentiate, an agent could easily select the wrong tool.
Tool names use a mix of verb-initial (ask_pipeworx, compare_entities) and noun-phrase patterns (entity_profile, dataset_info), with no consistent verb_noun structure. Naming is readable but lacks a predictable pattern.
With 34 tools, the server is on the heavy side. The broad scope (data querying, prediction markets, company research, local open data) somewhat justifies the count, but several tools could be consolidated (e.g., the various polymarket tools).
The tool set covers a wide range of functionalities including data querying, company research, prediction market analysis, and memory management. Minor gaps exist (e.g., no user authentication tools beyond subscriptions), but the surface is largely comprehensive for its intended purpose.