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 declare readOnly, idempotent, non-destructive. Description adds value by listing return fields (id, type, params, timestamps, fire_count). No contradictions.
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, front-loaded with purpose and return fields, then usage guidance. No waste.
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?
Complete for a simple list tool: schema covers params, annotations cover behavior, description lists return fields. No gaps.
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% (one parameter described). Description does not add extra meaning beyond schema; baseline 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?
Specific verb 'List', resource 'subscriptions', scope 'caller's active', and explicit return fields. Distinguishes from sibling subscribe/unsubscribe tools.
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?
Explicitly states when to use: 'review what you're monitoring before adding more or to find an id to cancel'. No direct alternatives named, but context with siblings makes it 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.
Most tools have distinct purposes, especially within the Roblox and Pipeworx domains. However, the three variants of ask_pipeworx (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are very similar and could cause confusion, as could deep_research vs ask_pipeworx.
Naming conventions are mixed: snake_case (user_followers_count), verb_noun with underscores (ask_pipeworx), and camelCase (recall, forget). Roblox tools follow a consistent 'user_' prefix, but Pipeworx tools lack a uniform pattern.
41 tools is excessive for a server named 'Roblox'. The majority of tools are Pipeworx data utilities, which are unrelated to the server's apparent focus. This overloading undermines coherence.
Coverage within the Roblox domain is basic (user profiles, friends, games) but misses common features like asset details or group management. Pipeworx appears comprehensive for data lookups, but the overall set lacks unified domain completeness.