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. The description adds caller scoping and return fields, but the 'active' default is redundant with the schema's include_inactive parameter description. No significant behavioral traits beyond what annotations/schema already convey.
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 fluff: purpose, return fields, and usage guidance all included efficiently and front-loaded.
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 list tool with one optional parameter and no output schema, the description covers purpose, return fields, and usage. It doesn't explicitly mention pagination or auth scope beyond 'caller's', but it's sufficiently complete given the tool's simplicity.
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% with a clear description for include_inactive. The tool description doesn't add parameter details beyond this, so baseline 3 is appropriate.
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 tool lists the caller's active subscriptions, with a specific verb ('list') and resource ('subscriptions'), and distinguishes it from siblings like subscribe/unsubscribe by specifying it's for reviewing existing monitoring.
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 usage contexts: 'review what you're monitoring before adding more' and 'to find an id to cancel.' It doesn't explicitly name alternative tools or give when-not guidance, but the context strongly implies subscribe/unsubscribe alternatives.
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.
Many tools have overlapping purposes, especially multiple ask_pipeworx variants and numerous Polymarket tools. Detailed descriptions help, but an agent could still confuse similar tools like ask_pipeworx and ask_pipeworx_beta.
Tool names use a mix of styles: some are descriptive (get_air_quality), some use proprietary prefixes (pipeworx_feedback), and others are arbitrary (bet_research). No consistent verb_noun pattern.
33 tools is excessive for a server named 'airquality', which only has 2 air-quality-specific tools. The count is appropriate for a general data platform, but mismatched with the server name.
For the air quality domain, the tool set is severely incomplete, missing historical data, pollution sources, and health recommendations. The overall set covers many other domains, but fails to address the server's apparent focus.