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. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), it discloses that the row is deactivated not deleted and that historical events remain accessible. No contradictions.
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 with action and resource, no redundant 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 mutation with no output schema, the description explains the effect (deactivation, not deletion, historical data preserved) and ownership rule, making it fully actionable.
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?
The description adds meaning by specifying the 'id' comes from 'subscribe', and schema already covers the parameter with 100% description coverage.
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 uses a specific verb ('Cancel') and resource ('subscription by id'), clearly distinguishing 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?
It explicitly states ownership enforcement ('you can only cancel your own subscriptions'), providing a key usage condition. It also links to 'recent_alerts' for historical data, aiding tool selection.
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 ask_pipeworx, ask_pipeworx_grounded, and deep_research, which all perform similar data retrieval. The multiple Polymarket tools also overlap in focus, making it unclear which to use for a given task.
Tool names are inconsistent: some use 'ask_', 'polymarket_', 'pipeworx_', while others like 'electricity_price', 'installed_power', and 'remember' follow no coherent pattern. Conventions are mixed and unpredictable.
With 35 tools, the server is over-scoped for an 'Energy Charts' purpose. Only 5-6 tools are directly energy-related; the rest are a miscellany of data services, prediction markets, and memory functions, which is excessive and unfocused.
The server lacks essential energy analysis tools like forecast, emission factors, or capacity utilization, yet includes many unrelated tools (e.g., betting, memory). This creates significant gaps for the stated domain.