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=true, idempotentHint=true, destructiveHint=false. Description adds that it returns specific fields, but no new 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, front-loaded with purpose, no wasted words. Ideal length and structure.
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?
Given low complexity (1 optional param, no output schema, rich annotations), the description fully covers purpose, return values, and usage context.
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 single parameter (include_inactive) with full description, so description adds no additional parameter meaning beyond what's already in 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?
Clearly states 'List the caller's active subscriptions' and enumerates returned fields (id, type, etc.). Distinguishes from sibling tools like subscribe/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?
Provides explicit use cases: 'review what you're monitoring before adding more' and 'find an id to cancel.' Could mention that searching is not needed, but context is sufficient.
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, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, and validate_claim all route factual questions to data sources, making it hard to pick the right one. The server name 'Football Data' is misleading because most tools are unrelated to football, and the few football tools are distinct but swamped by the general-purpose data platform.
There is a mix of conventions: some tools follow verb_noun (get_competition_matches, list_competitions, scan_dependency, resolve_entity), but many are noun phrases (entity_profile, polymarket_arbitrage, pipeworx_trending, deep_research) or verb-only (remember, forget, subscribe). The use of the 'pipeworx' and 'polymarket' prefixes is inconsistent across the set.
36 tools is excessive for a server named 'Football Data', especially since only 5 tools are football-specific. The majority are general-purpose data/research tools that belong in a separate server, inflating the count and diluting the server's focus.
The football surface is incomplete: there are tools for listing competitions, getting matches, standings, and team details, but no player stats, match events, head-to-head records, or live score details. While the incidental general-purpose tools are extensive, they don't fill the gaps in the server's stated football domain.