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?
Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description adds critical context: 'The row is deactivated (not deleted) so its historical events stay available via recent_alerts.' This clarifies the non-destructive, soft-delete behavior and links to a sibling tool.
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 that are front-loaded and efficient. Every sentence adds unique information: purpose, ownership constraint, and behavioral nuance. No wasted words.
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 simple single-parameter tool with no output schema, the description covers purpose, usage condition, and behavioral effect. It references relevant sibling tools and provides complete guidance.
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?
With 100% schema coverage, baseline is 3. The description adds value by noting the id is a UUID and that it comes from subscribe, helping the agent understand the parameter's origin and format.
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', using a specific verb and resource. It naturally distinguishes from sibling tools 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?
The description explains ownership enforcement ('you can only cancel your own subscriptions'), which guides when to use. It doesn't explicitly mention when not to use, but the condition is clear.
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 (e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded are nearly identical; bet_research and polymarket_edges both analyze Polymarket markets). Descriptions are detailed but the sheer number of similar tools creates ambiguity for agents.
Most tools follow a verb_noun pattern (e.g., list_subscriptions, create_subscription), but a few use noun_verb (bet_research) or are standalone nouns (centroid, midpoint). Overall, the pattern is fairly consistent despite minor deviations.
35 tools is on the high side for an MCP server. The scope is broad (data access, prediction markets, geospatial, memory, subscriptions), so each tool earns its place, but the number is borderline for coherence.
The tool set covers a wide range of functionalities: data querying, entity profiles, comparisons, prediction market analysis, geospatial, memory, subscriptions, etc. Minor gaps exist (no batch operations or data export), but the core workflows are well-supported.