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. The description adds value by specifying the exact fields returned (id, type, params, timestamps, fire_count) and the option to include inactive subscriptions, providing behavioral context beyond the 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 concise sentences: first states the purpose and return fields, second gives usage context. No redundant words, and the critical information is front-loaded.
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 list tool with one optional parameter and no output schema, the description covers purpose, returned fields, and appropriate usage context. No gaps are apparent.
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% with the 'include_inactive' parameter well-described. The description implies default behavior (active only) but adds no new semantic details beyond the schema. Baseline of 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 states 'List the caller's active subscriptions' with a clear verb and resource, and lists the returned fields. It differentiates from sibling tools like 'subscribe' and 'unsubscribe' by focusing on listing rather than mutating 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 the tool to review current subscriptions before adding more or to find an ID to cancel. While it doesn't name alternatives like 'subscribe' or 'unsubscribe' directly, the context of siblings and the usage hint make the guidance clear.
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.
Tools are mostly distinct but there is some overlap among lookup tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, entity_profile) and among Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage). Agents might occasionally struggle to choose the right one.
Naming is inconsistent: some use verb_noun snake_case (ask_pipeworx, compare_entities), some are single words (forget, recall, remember), and others are noun-based (compliance_catalog, entity_profile). No consistent pattern.
With 34 tools, the count is too high for a server named 'ISO Standards'. The majority of tools are unrelated to ISO standards (e.g., Polymarket, memory, web scraping), making the scope highly inappropriate.
As an ISO standards server, the tool set is severely incomplete. Only 4-5 tools (search_standards, get_standard, compliance_catalog, open_data_files) actually deal with ISO standards. Essential operations like comparing standards or browsing revisions are missing.