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 annotations, the description reveals crucial behavior: the row is deactivated (not deleted) and historical events remain available via recent_alerts. Ownership enforcement is also disclosed, adding context not present in structured metadata.
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 three short sentences, front-loaded with the primary action, then adding crucial nuances. No filler or repetition; every sentence carries meaningful 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, the description covers the action, constraints (ownership), and post-condition (deactivation with retained history). Annotations handle idempotency and non-destructiveness, making this complete.
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% and the only parameter 'id' is already well-described as a subscription UUID returned by subscribe. The description adds no extra semantic detail beyond restating 'by id', so the baseline 3 applies.
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 verb ('Cancel') and resource ('a subscription by id'), clearly distinguishing its purpose from sibling tools like 'subscribe' and 'list_subscriptions'. The ownership enforcement further clarifies scope.
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 explicitly states a key condition: 'you can only cancel your own subscriptions', which serves as a when-not restriction. The note about deactivation and historical events also helps an agent decide whether this tool is appropriate.
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 have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all answer data questions, while discover_tools and suggest_questions both serve discovery. The three ArcGIS tools are distinct but are drowned out by the unrelated Pipeworx and prediction-market tools, making it hard to pick the right one.
Tool names are mostly snake_case but mix verb_noun (query_layer, search_datasets, remember), noun_noun (layer_info, entity_profile), and less conventional forms (search_within, generate_llms_txt). The naming is readable and not chaotic, but there is no single consistent pattern across the set.
34 tools is excessive for a server named 'Arcgis Palmbeach'. Only 3 tools are GIS-related (search_datasets, query_layer, layer_info); the other 31 are unrelated Pipeworx data, prediction-market, and memory utilities. The count grossly mismatches the server's apparent purpose.
For the stated ArcGIS/Palm Beach County GIS purpose, the tool surface is severely incomplete: only search, query, and layer-schema lookup exist, with no data editing, feature operations, or map-service management. While the Pipeworx domain is heavily covered, that is not what the server name promises, so the surface is a poor fit.