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=false. Description adds that it returns specific fields (id, type, etc.) and implies user-specific scoping. 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?
Two concise sentences with no fluff. Key information is front-loaded: what it does, what it returns, and when to use it.
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 no output schema, the description lists return fields. Parameter is well-documented in schema. The tool is simple and the description fully equips an agent to use it correctly within the sibling 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 with 100% coverage. Description mentions 'active subscriptions' which aligns with the default behavior of the include_inactive parameter, adding context beyond 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 the tool lists the caller's active subscriptions. Distinguishes from sibling tools like subscribe and unsubscribe by focusing on reading existing 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?
Explicitly advises using this tool to review subscriptions before adding more or to find an id to cancel, providing clear when-to-use guidance.
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.
ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, creating direct ambiguity. The five polymarket tools and the ask/research/entity family (ask_pipeworx, deep_research, entity_profile, compare_entities, recent_changes) also blur boundaries, making selection error-prone.
Most names are snake_case with useful domain prefixes (detroit_*, polymarket_*, ask_pipeworx_*), but verb styles vary widely (ask, generate, scan, validate, suggest, remember) and some names like recent_changes vs recent_alerts are confusable. No strict pattern unifies the set.
At 34 tools the server is overloaded; alongside the core universal-data and Detroit-query tools it also carries memory, subscriptions, feedback, AI-visibility, and npm-scanning tools that feel outside the stated scope. Many of these could be split into separate servers or trimmed.
The query surface is broad and the memory/subscription sub-domains have full lifecycle coverage, but the 'Data Detroit' identity is thin (only three city-specific tools) and the catalog-heavy design relies heavily on meta-tools rather than direct data operations. Some gaps remain, like a straightforward way to fetch a raw record by citation.