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. Description adds the return structure but does not disclose additional behavioral traits beyond annotations.
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: first states purpose and outputs, second provides usage guidance. No superfluous 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 simple tool with one optional parameter and no output schema, the description lists all return fields and provides usage context. Complete given annotations.
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 includes a description for the only parameter. Description does not add 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 clearly states 'List the caller's active subscriptions' and enumerates returned fields. It distinguishes from sibling tools 'subscribe' and 'unsubscribe' by focusing on listing.
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?
Provides explicit usage context: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' Does not mention when not to use, but context is sufficiently clear.
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 overlapping purposes: ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are nearly identical; Polymarket tools (bet_research, polymarket_arbitrage, polymarket_edges, etc.) are hard to distinguish; memory tools (remember, recall, forget) and subscription tools (subscribe, unsubscribe, list_subscriptions, recent_alerts) also create ambiguity.
Tool names mix snake_case (find_stations, get_station) with inconsistent verbs and noun phrases (ai_visibility_check, entity_profile, validate_claim). No clear pattern emerges, and some names are verbose or unclear (e.g., scan_competitor_ai_presence).
At 33 tools, the set is too large for a focused server. Many tools are unrelated to the server name 'Openchargemap' (EV charging), and the collection feels like a grab bag of unrelated functionalities (Pipeworx data, Polymarket betting, AI visibility, memory management).
For the implied domain of EV charging, only two tools exist (find_stations, get_station), leaving major gaps (no CRUD). As a general utility, it lacks coverage in many areas (e.g., no file handling, no scheduling). The set is incomplete both as a domain-specific and general-purpose server.