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 that the row is deactivated rather than deleted, and explains the consequence (historical events remain available via recent_alerts). This goes beyond the annotations' safety hints, which only indicate non-destructive and idempotent behavior.
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 with no filler. The first sentence states the action, the second adds constraints and side effects. Everything present 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?
Given the simple tool signature (one param, no output schema), annotations already describe safety profile. The description covers purpose, ownership, and the deactivation behavior, plus its relationship to recent_alerts. No gaps remain.
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?
Schema coverage is 100% — the id parameter is fully described as 'Subscription id (uuid) returned by subscribe.' The description adds nothing beyond 'by id,' but the schema already carries the burden.
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 opens with 'Cancel a subscription by id,' which is a specific verb+resource pair. It further clarifies the ownership constraint, distinguishing it 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?
States when to use (cancel a subscription by id) and an explicit constraint ('you can only cancel your own subscriptions'). Does not explicitly contrast with alternatives like list_subscriptions or subscribe, but the purpose is clear enough.
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.
Multiple tools overlap heavily: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are nearly identical routers, the six polymarket tools cover similar prediction-market territory with fuzzy boundaries, and the deps.dev tools (package/version/dependencies/query/scan_dependency) all deliver dependency metadata. An agent would frequently need the lengthy descriptions to pick the right one.
Tool names mix several conventions: noun-only names (package, version, query, project, dependencies), verb_noun names (scan_dependency, validate_claim, resolve_entity), and family-prefixed names (ask_pipeworx_*, polymarket_*, pipeworx_*). There is no single consistent pattern across the set.
With 36 tools, the server is well past the 'heavy' threshold. The scope is also sprawling: general data querying, dependency lookup, memory management, subscriptions, prediction markets, claim verification, and AI-visibility scanning. Many tools could be consolidated or moved to separate servers.
The tool set is individually broad and covers many workflows, but the server's stated identity ('Deps Dev') does not match the dominant Pipeworx data surface, creating an unclear core purpose. Within the dependency sub-domain it is fairly complete, and the data-research workflows have decent coverage, but gaps like subscription updates and true deps.dev ecosystem coverage suggest the surface is improvised.