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?
The description discloses that the operation is a soft delete ('deactivated, not deleted') and mentions the side effect on historical events. This adds behavioral context beyond the annotations (which only indicate non-destructive and idempotent hints), making the tool's behavior fully transparent.
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 concise at two sentences, front-loads the primary action, and uses the second sentence for necessary caveats without redundancy. Every word adds value.
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, the description covers purpose, constraints, and side effects sufficiently. The ownership rule and soft-delete nature are critical context that is fully addressed.
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 input schema already provides a complete description of the single 'id' parameter ('Subscription id (uuid) returned by subscribe'), so the description adds little semantic value for the parameter itself. The baseline of 3 applies because schema coverage is 100%.
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 states a specific action ('Cancel a subscription by id') with a clear resource and method. It distinguishes itself from sibling tools like 'subscribe' and 'list_subscriptions' by focusing on cancellation, and also notes ownership enforcement and soft-deletion behavior.
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 ('you can only cancel your own subscriptions') provides clear context for when this tool is applicable. However, it does not explicitly name alternatives or state when not to use it, though the purpose is unambiguous.
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.
Each tool has a highly specific purpose with detailed descriptions, making them easily distinguishable. Overlaps are minimal; for instance, Pipeworx and Polymarket tools have distinct roles within their domains.
Most tools follow a consistent snake_case pattern (e.g., ask_pipeworx, compare_entities), but a few single-word names (e.g., forget, recall) deviate slightly, causing minor inconsistency.
The server is named 'recipes' but contains only 4 recipe-related tools out of 34. The majority cover unrelated domains like finance, betting, and data queries, making the scope overly broad and misaligned with the server name.
For the 'recipes' domain, essential CRUD operations and features like meal planning are missing. While the general tool set is extensive, it lacks critical recipe-related functionality, leaving significant gaps for the intended purpose.