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 provide readOnlyHint, idempotentHint, and destructiveHint. The description adds return field details and parameter behavior (include_inactive), but does not disclose additional behavioral traits beyond what annotations already cover.
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 purpose and usage. Every sentence adds value with no redundancy.
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?
The description fully covers purpose, usage, returned fields, and parameter behavior for this simple tool. No gaps given the lack of output schema and single optional parameter.
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 the baseline is 3. The description does not add new meaning beyond the schema's description for the single parameter; it only reiterates the default behavior.
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 tool lists the caller's active subscriptions and explicitly lists returned fields (id, type, params, created_at, last_fired_at, fire_count). This distinguishes it from siblings 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?
The description explicitly states when to use this tool: 'review what you're monitoring before adding more or to find an id to cancel.' This provides clear context and 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.
Several tools serve nearly identical purposes: ask_pipeworx and ask_pipeworx_beta are currently functionally identical, and polymarket_edges, polymarket_arbitrage, and bet_research all hunt prediction-market opportunities with overlapping outputs. The verbose descriptions help, but an agent can easily call the wrong one.
All 33 names use lowercase snake_case with descriptive, mostly verb-first words (ask_, compare_, discover_, search_), and domain suites are consistently prefixed (polymarket_*, pipeworx_*). Minor deviations like entity_profile or recent_changes (noun/adjective-first) keep it from a perfect 5.
33 tools is well into the 'too many' range, especially for a server nominally about the narrow Complex Portal database. Many tools (memory, feedback, subscriptions, trending) are generic meta-utilities unrelated to the stated purpose.
For the stated 'Complex Portal' domain, only search_complexes and get_complex exist, with no organism-scoped search, batch access, or additional lifecycle coverage, making the surface severely incomplete for that name. The actual Pipeworx platform is broadly covered, but the server-name mismatch makes the set feel incomplete for its advertised purpose.