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 cover readOnly, idempotent, non-destructive. Description adds that it returns specific fields and defaults to active subscriptions, complementing annotations well.
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, followed by usage guidance. No superfluous text.
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 listing tool: describes purpose, return fields, parameter effect, and usage context. No output schema needed as return fields are listed.
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 covers the one parameter with 100% coverage. Description adds context by explaining 'active' default and that include_inactive includes cancelled subscriptions, enhancing meaning.
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?
Description clearly states 'List the caller's active subscriptions' with specific verb and resource, and distinguishes from siblings like subscribe and unsubscribe by implying listing existing ones.
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 tells when to use: 'to review what you're monitoring before adding more or to find an id to cancel', providing clear context relative to siblings.
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 are near-duplicates: ask_pipeworx and ask_pipeworx_beta are explicitly described as identical, while ask_pipeworx_grounded, deep_research, and validate_claim all route factual questions through overlapping retrieval pipelines. The visa tools are distinct, but the overall set has too many fuzzy boundaries for an agent to reliably pick the right one.
Names are consistently lowercase snake_case with recognizable prefixes such as ask_pipeworx, polymarket_, visa_, and verb-first names like compare_entities, resolve_entity, and validate_claim. Minor deviations like bare verbs (forget) and noun-phrase names (entity_profile, pipeworx_feedback) keep it from a perfect score.
34 tools is already above the 25-tool heavy threshold, and for a server named 'Visa Requirements', only 3 tools are visa-related; the rest form an unrelated general data, research, prediction-market, and memory toolkit. This is an over-scoped and confusingly mixed-purpose collection.
The three visa tools cover passport-to-destination checks, all destinations for a passport, and multi-passport comparison, but there is no reverse destination-to-passport lookup or visa-policy/application detail. The unrelated tools do not fill those visa-domain gaps, so the surface feels incomplete for the stated visa purpose.