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 already indicate mutation (readOnlyHint=false), non-destructiveness (destructiveHint=false), and idempotency. The description adds valuable context: the row is deactivated (not deleted) and historical events remain available via recent_alerts. 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?
The description is two sentences with zero waste. The first sentence states the primary action, and the second covers ownership and behavioral details. Every sentence earns its place.
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 tool with one parameter, full schema coverage, and good annotations, the description completely covers purpose, parameter source, ownership constraint, soft delete behavior, and link to related tool (recent_alerts). No gaps.
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, the schema already describes the 'id' parameter. The description adds extra context by noting the id is 'returned by subscribe', which helps the agent understand how to obtain it. This slightly exceeds 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' with a specific verb and resource. It distinguishes itself from siblings like 'subscribe' and 'list_subscriptions' by emphasizing ownership enforcement and soft deletion.
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 explicitly states 'Ownership is enforced — you can only cancel your own subscriptions,' providing clear guidance on when to use the tool. It does not mention alternatives or when not to use, but the constraint is strong.
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 clearly distinct purposes due to detailed descriptions and specific domains. However, there is potential for confusion between `ask_pipeworx` and `ask_pipeworx_grounded` (both route to data), and among the four polymarket tools, which could cause misselection if not read carefully.
Naming is inconsistent: while all use snake_case, they mix verbs (`ask_`, `list_`, `bet_`, `scan_`), noun phrases (`entity_profile`, `product_details`, `recent_alerts`), and imperative verbs (`forget`, `remember`, `recall`). No single pattern is followed throughout, making it harder to predict tool names.
With 31 tools, the server covers multiple domains (energy, general data, betting, memory, subscriptions) which feels heavy for a single server named 'Octopus Energy'. While each tool has a role, the scope is overly broad, and many tools are tangential to energy, suggesting the number could be reduced or better scoped.
For the energy domain, tools are present but only cover listing products and tariffs, missing account management or switching. For the broader domains (data, prediction markets), coverage is decent but lacks some expected features like browsing all available data sources or user profile management. The set is not fully comprehensive for any single purpose.