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 indicate readOnlyHint, idempotentHint, and destructiveHint false. The description adds return field details and the scope 'caller's active subscriptions', providing useful behavioral context 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, no wasted words. The core function and return fields are stated first, followed by usage guidance. Excellent structure and conciseness.
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 one optional parameter, no output schema, and annotations covering safety, the description covers the essential aspects. Slight room for improvement by explicitly mentioning default behavior (active only), but it's implied.
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 has 100% description coverage for the single parameter 'include_inactive'. The description does not add extra meaning beyond the schema, so baseline score 3 is appropriate.
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 verb 'List' and the resource 'the caller's active subscriptions', with specific return fields (id, type, params, etc.). This 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?
Provides explicit guidance: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' It does not explicitly mention when not to use, but the context is clear enough.
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 genuinely easy to confuse: ask_pipeworx and ask_pipeworx_beta are explicitly described as currently identical, and the five polymarket_* tools overlap significantly in purpose. There are also wrapper-like pairs such as ai_visibility_check vs. scan_competitor_ai_presence and entity_profile vs. recent_changes vs. compare_entities that require reading long descriptions to disambiguate.
The names are mostly lowercase snake_case and readable, but there is no consistent verb_noun pattern: entity_profile and recent_changes are noun phrases, pipeworx_trending and pipeworx_feedback use a prefix, ask_pipeworx_beta is a single-family variant, and scan_competitor_ai_presence uses a different structure from ai_visibility_check. The naming is not chaotic, but it is a mix of conventions.
A server labeled Microsoft Onenote exposes 31 tools, none of which actually relate to OneNote note-taking, notebooks, or pages. Even as a general research/prediction-market server, 31 tools is far above the coherent range, and for the stated product purpose this count is wildly inappropriate.
For the server's declared OneNote domain, there is zero coverage: no tools for creating, reading, updating, or deleting notes, pages, sections, or notebooks. The actual tool surface is centered on Pipeworx data lookups, Polymarket arbitrage, and memory helpers, which leaves the apparent note-taking domain completely unrepresented.