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), description adds that row is deactivated (not deleted) and historical events remain, providing critical behavioral context.
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?
Three concise sentences with no waste: action, ownership constraint, and side effects all efficiently communicated.
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 tool with one parameter and no output schema, description fully covers action, constraint, and outcome, making it complete.
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% with parameter description 'Subscription id (uuid) returned by subscribe.' Description adds minimal extra meaning beyond confirming 'by id'.
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?
Description clearly states 'Cancel a subscription by id' with specific verb and resource, distinguishing 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?
Ownership enforcement is explicitly stated ('you can only cancel your own subscriptions'), clarifying when to use. No explicit alternatives mentioned, but context 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.
Most tools have detailed descriptions that clearly delineate their purposes, but ask_pipeworx_beta is currently functionally identical to ask_pipeworx, and deep_research overlaps with ask_pipeworx for multi-part questions. The six polymarket_* tools also share related territory, though their boundaries are well-documented.
All names use snake_case, and domain prefixes like polymarket_, pipeworx_, and ask_ add predictability. However, the set mixes verb-led names (compare_entities, resolve_entity, search_within) with noun-led names (entity_profile, recent_changes, bet_research), so there is no single consistent verb_noun convention.
35 tools is well above the 15-25 'heavy' band and feels like a kitchen sink: the server bundles a data-research platform, prediction-market analysis, memory, subscriptions, number conversions, and web-dev utilities into one surface. Many of these are unrelated to the server's 'Numbers' identity.
The main subdomains are thoroughly covered: data lookup (ask_pipeworx variants, deep_research, validate_claim), prediction-market analysis (arbitrage, edges, fill risk, kalshi spread), memory (remember/recall/forget), and subscriptions (subscribe/list/unsubscribe/recent_alerts). Minor gaps exist, such as no subscription update operation, but core lifecycle coverage is strong.