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, covering safety. The description adds value by listing specific return fields (id, type, etc.) and indicating that active subscriptions are returned by default, with an optional include_inactive parameter. 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?
The description is extremely concise: two sentences that efficiently convey purpose, return fields, and usage guidance. Every sentence earns its place with no wasted words.
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?
Despite lacking an output schema, the description fully compensates by enumerating return fields. It covers default behavior, optional parameter, and usage context. Combined with annotations, this is complete for a simple read-only list tool.
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% for the single parameter (include_inactive), and its schema description is already clear. The tool description does not add any new semantic information about the parameter beyond what the schema provides.
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 'List the caller's active subscriptions' which is a specific verb-resource combination. It distinguishes itself from sibling tools like 'subscribe' and 'unsubscribe' by focusing on listing rather than creating or deleting subscriptions.
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 explicit usage guidance: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' This tells the agent when to use it, though it does not explicitly mention alternatives like 'subscribe' or 'unsubscribe'.
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, e.g., three versions of ask_pipeworx for similar tasks, and several research/analysis tools (bet_research, deep_research, entity_profile) with unclear boundaries. The mix of Europeana-specific tools with a broad research toolkit creates confusion.
Tool names are inconsistent, mixing snake_case (ai_visibility_check, ask_pipeworx), verb_noun patterns (compare_entities, resolve_entity), and short names (search, record, forget). No clear naming convention is followed throughout the set.
33 tools is excessive for a Europeana-focused server, as only 3 tools (search, record, search_within) are directly related to Europeana. The rest are a broad, unrelated toolkit, making the server feel like a kitchen sink rather than a cohesive collection.
The Europeana-specific tool surface is severely incomplete, lacking browse collections, advanced filters, or entity linking. The inclusion of many unrelated tools does not compensate for the gaps in the core domain, resulting in a poorly scoped offering.