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 goes beyond the annotations by explicitly disclosing ownership enforcement ('you can only cancel your own subscriptions') and the deactivation behavior ('row is deactivated (not deleted)'). These are meaningful behavioral traits not captured by readOnlyHint or destructiveHint.
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 deliver the core purpose, a critical constraint (ownership), and a key behavioral detail (soft delete) without any fluff. The description is front-loaded with the verb and resource, and every clause carries information.
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 mutation tool with no output schema, the description explains the action, the ownership rule, and the post-cancellation behavior, making it self-contained. The reference to recent_alerts provides additional context for the tool's effect.
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 fully documents the single parameter 'id' with a clear description. The tool description adds no parameter-specific detail beyond what the schema provides, and 100% schema coverage sets the baseline at 3.
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') and the specific resource. It differentiates from siblings by noting ownership enforcement and deactivation instead of deletion, making the tool's scope unmistakable.
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?
The description provides clear context for when to use the tool (canceling subscriptions) and implies exclusion via the soft-delete note (historical events remain available via recent_alerts). However, it does not explicitly name alternative tools or state when not to use it, so it stops short of a 5.
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.
Several clusters of similar tools exist: ask_pipeworx, ask_pipeworx_beta (identical right now), and ask_pipeworx_grounded are easily confused, and the many polymarket_* tools overlap heavily. However, the extremely detailed descriptions usually clarify the specific intent, so an agent can often pick correctly.
Tool names are uniformly snake_case and mostly follow verb_noun or a recognizable prefix pattern (ask_, polymarket_, pipeworx_). There are a few noun-phrase exceptions like layer_info and entity_profile, but the style is consistent enough that naming is not a major source of confusion.
34 tools is heavy for any server, and especially for one named 'Arcgis Montana' where only three tools (search_datasets, query_layer, layer_info) relate to GIS. Most of the surface is a general-purpose data/analytics API, making the count feel bloated and unfocused.
Relative to the implied ArcGIS Montana purpose, the surface is severely incomplete: it only supports searching and querying datasets, with no create/update/delete or administrative capabilities. The Pipeworx functionality is broad, but the GIS side is a thin slice, leaving obvious gaps for geospatial workflows.