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 the annotations, the description explains ownership enforcement, that the row is deactivated (not deleted), and that historical events remain available via recent_alerts. This adds meaningful behavioral nuance absent from just the 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?
Two sentences, front-loaded with the primary action and followed by essential caveats. Every word earns its place, with no redundancy or filler.
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 single-parameter tool with no output schema, the description covers the action, ownership constraints, the deactivation behavior, and the impact on historical data. It is fully sufficient for an agent to know how and when to invoke it.
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 schema already documents the id parameter fully (including that it comes from subscribe). The description merely says 'by id' without adding semantics beyond the schema, so it meets the baseline for full schema 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 clearly states the action ('Cancel a subscription by id') with a specific verb and resource, and it naturally distinguishes itself from siblings like subscribe and list_subscriptions. The purpose is unambiguous and immediately understandable.
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 sets a clear usage condition ('you can only cancel your own subscriptions') and implies the id comes from subscribe, but it doesn't explicitly name alternatives or non-use cases. The context is sufficient given there is only one unsubscribe tool.
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.
Tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, and entity_profile have overlapping purposes, causing potential confusion. However, their descriptions provide some differentiation, so an agent can usually pick the right one with careful reading.
Naming is highly inconsistent: mixes verb_noun (ask_pipeworx), noun_verb (reverse_dns), single-word (geoip), and compound phrases (generate_llms_txt). No clear pattern, making it hard for an agent to predict tool names.
44 tools is overwhelmingly high for a single server. The set mixes unrelated domains (network tools, data APIs, memory, prediction markets), suggesting it's a grab bag rather than a focused toolkit.
The server lacks a coherent domain, so evaluating completeness is difficult. There are many lookup tools but few for updates or deletes (except memory). The HackerTarget subset is sparse, and the overall surface feels incomplete for any single purpose.