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 safety (readOnlyHint, idempotentHint, destructiveHint false). Description adds return fields and scope, but no additional behavioral nuance beyond what annotations imply.
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 concise sentences, front-loaded with main purpose. 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?
Given simple schema (1 optional param) and no output schema, description fully covers purpose, usage, return fields, and retrieval 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 coverage is 100%, so description need not elaborate. It does not add meaning beyond the schema's parameter description.
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' with specific verb and resource, and 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?
Explicitly says when to use: 'before adding more or to find an id to cancel', providing clear context and alternatives.
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.
The tool set is extremely heterogeneous and overlapping. Multiple tools serve nearly identical purposes (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, suggest_questions), and entity-related tools (get_entity, get_wikidata_facts, entity_profile, compare_entities, resolve_entity) have unclear boundaries. The server is named Wikidata but only 3 of 34 tools actually relate to Wikidata, causing confusion about which tool is appropriate.
Tool names mix multiple conventions: verb_noun (get_entity, search_entities, list_subscriptions), noun phrases (polymarket_edges, entity_profile, pipeworx_feedback), and inconsistent suffixes (_beta, _grounded). The verbs used are vague and not part of a coherent pattern (get, search, ask, discover, resolve, scan, validate, generate, remember, recall). The naming is readable but lacks a predictable system.
34 tools is high for a server with a focused name like Wikidata, and nearly all tools belong to unrelated domains (Pipeworx data routing, Polymarket betting, memory management, subscriptions, AI visibility). The count appears bloated and scattered rather than well-scoped; most tools could be split into separate servers.
For a Wikidata server, the coverage is minimal: only search, get by ID, and human-readable facts are present, with no SPARQL query support or property-level access. The majority of tools address Pipeworx's broad data catalog, leaving the advertised Wikidata purpose severely under-served. The surface is complete for a different domain but incomplete for the stated one.