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?
Discloses ownership enforcement and soft-delete behavior (deactivated, not deleted), adding value beyond annotations that show non-destructive and idempotent.
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, no fluff, front-loaded with action and constraint.
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?
Simple tool with one required param and no output schema; description covers purpose, constraint, and behavior sufficiently.
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?
Only one parameter with full schema coverage; description merely says 'by id' without adding extra meaning beyond schema.
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?
Clear verb 'cancel' with resource 'subscription'. Distinct 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?
States ownership constraint and that the row is deactivated not deleted, but does not explicitly mention when to use vs alternatives.
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 distinct purposes, but ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are very similar, causing potential confusion. The memory tools (remember/recall/forget) are separate, but the overall set is diverse enough that agents can typically distinguish them.
Tool names use a mix of camelCase (ask_pipeworx, entity_profile, generate_llms_txt) and snake_case (http_status, list_http_statuses, list_subscriptions), with no consistent verb_noun pattern. Some names are descriptive, but the lack of a unified convention hurts predictability.
33 tools is high for a server named 'Httpstatus' that only has two HTTP-related tools. The large number spans data retrieval, memory, subscriptions, prediction markets, and more, making the server feel bloated and unfocused.
The server covers many domains but each is incomplete. HTTP status has lookup and list but no lifecycle. Memory tools are basic. Data retrieval is extensive but not exhaustive for any single domain. It's a broad but shallow collection.