list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
| Name | Required | Description | Default |
|---|---|---|---|
| include_inactive | No | Include cancelled subscriptions in the response (default false). |
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?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds valuable context by listing the exact return fields (id, type, params, created_at, last_fired_at, fire_count) and clarifying that it returns only active subscriptions by default. This goes beyond the annotations without contradicting them.
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 two sentences: the first states the action and return fields, the second gives usage guidance. It is front-loaded with the core purpose, contains no fluff, and every sentence 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?
For a simple read-only list tool with one optional parameter, the description is complete: it explains what it does, what it returns, and when to use it. There is no output schema, so the explicit list of return fields is especially valuable. The annotations handle safety semantics, and the schema handles parameter details.
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 schema fully covers the single optional parameter include_inactive with a clear description, so schema coverage is 100%. The tool description does not mention this parameter, but it does not need to because the schema is self-sufficient. The baseline of 3 is appropriate since the description adds no extra parameter meaning beyond the 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?
The description starts with a specific verb and resource: 'List the caller's active subscriptions.' It clearly distinguishes the tool from siblings by focusing on listing, while siblings like subscribe/unsubscribe handle mutations. It also specifies the scope ('caller's') and the default filter ('active').
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 gives explicit usage context: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This implies when to use it in relation to adding or canceling subscriptions. However, it does not explicitly name sibling tools like subscribe or unsubscribe as alternatives, so it stops short of a perfect score.
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 tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and discover_tools all provide data lookup/research. The PolyMarket family (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) also creates boundary confusion despite varied signals.
Most tools use snake_case, but the naming pattern is mixed: some are imperative verb phrases (query_layer, validate_claim), while others are noun phrases (entity_profile, recent_alerts, layer_info). Descriptions are readable overall, but there is no consistent verb_noun convention across the set.
34 tools is high and the vast majority are unrelated to the server's stated ArcGIS Abbotsford purpose. The set appears to be a generic Pipeworx data/prediction-market toolkit with only a few GIS-specific tools, making the count excessive for the declared scope.
For the ArcGIS Abbotsford domain, the surface is severely incomplete: only search_datasets, query_layer, and layer_info cover GIS functionality, lacking update/delete/create operations or broader dataset management. For the actual Pipeworx domain, coverage is decent, but that does not match the server name.