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 readOnly and idempotent, and the description adds useful context about scope (caller's subscriptions) and default behavior (active only, with the include_inactive parameter). It doesn't contradict annotations and provides meaningful behavioral detail beyond safety flags.
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 action and return fields, second gives usage context. No fluff, front-loaded, every word 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?
With no output schema, the description explicitly names return fields. The single optional parameter is explained in the schema, and the tool's role relative to subscribe/unsubscribe is clearly stated. The description is complete for an agent to select and call the tool correctly.
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 input schema covers the single parameter include_inactive with a clear description. The tool description does not need to add more, as schema coverage is 100%; 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 clearly states the tool lists the caller's active subscriptions and enumerates the returned fields (id, type, params, etc.). This specific verb+resource combination distinguishes it from sibling tools like subscribe and unsubscribe.
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 when-to-use guidance: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This differentiates it from subscribe/unsubscribe and covers the main use cases.
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 responsibilities: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all serve similar lookup purposes. entity_profile, compare_entities, and recent_changes all retrieve company data. Several Polymarket tools overlap in edge detection. The large number of tools with fuzzy boundaries makes it difficult for an agent to select the correct one.
Tool names are a mix of conventions: some use verb_noun (lookup_postcode, validate_postcode, resolve_entity), others are verb_phrase (ask_pipeworx, deep_research, suggest_questions), and a few are compound (polymarket_arbitrage, scan_competitor_ai_presence). No uniform pattern, though the structure is readable.
Despite being named 'postcodes', only 4 of 35 tools are directly about postcodes. The vast majority belong to a broad data platform (Pipeworx) with specialized tools for finance, betting, news, etc. The count is excessive for a focused service, and many tools are only useful for users of that platform, leading to clutter.
For a postcode server, the tools cover basic needs (lookup, nearest, random, validate). However, the server's actual scope is much larger; within that broader scope, there are notable gaps: no general text search, no direct access to raw SEC filings, and many tools depend on paid plans or external accounts. The coverage is uneven and incomplete for a unified data platform.