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). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read nature is covered. The description adds value by specifying return fields and the default behavior of excluding cancelled subscriptions, exceeding what annotations alone provide.
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, front-loaded with the core action, and no wasted words. The second sentence delivers return field details and usage guidance efficiently.
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?
For a simple read-only tool with one optional parameter and no output schema, the description fully covers purpose, return values, and use cases. It is complete enough for an agent to invoke correctly.
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 schema description for include_inactive is fully descriptive ('Include cancelled subscriptions in the response (default false)'), with 100% coverage. The tool description adds no additional parameter semantics, so the baseline 3 applies.
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?
Description clearly states the verb 'List' and the resource 'caller's active subscriptions', and it lists the return fields. This unambiguously 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?
Explicit usage context is provided: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' While it doesn't mention alternatives, the use case is clearly scoped and actionable.
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 mixes two unrelated domains (Star Wars and Pipeworx data services), which is initially confusing. Within the Pipeworx suite, tools like ask_pipeworx and ask_pipeworx_grounded are clearly differentiated, but some overlap exists (e.g., deep_research vs. compare_entities both do multi-source lookups). Overall, most tools have distinct purposes, but the domain mismatch lowers clarity.
All tools use snake_case consistently (e.g., ask_pipeworx, entity_profile, resolve_entity). The naming pattern is mostly verb_noun or descriptive_compound, which is predictable. Minor deviation: some tools start with a verb (ask_pipeworx) while others start with a noun (entity_profile), but the style is uniform.
34 tools is on the high side but not unreasonable for a data-heavy server. However, the set covers two distinct domains (Star Wars and Pipeworx), making it feel bloated. The count could be reduced by separating the domains or pruning rarely-used tools.
The Pipeworx side appears comprehensive, covering queries, profiles, comparisons, subscriptions, alerts, and memory. The Star Wars side is incomplete—it lacks tools for vehicles, species, or individual characters (only search_people exists). The overall surface has gaps in one of its two domains.