unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id (uuid) returned by subscribe. |
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?
Adds behavioral detail beyond annotations: explains that the row is deactivated (not deleted) and historical events stay available via recent_alerts. No contradictions with 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?
Three sentences, each serving a distinct purpose: action, ownership constraint, and behavioral effect. No unnecessary words.
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 one-parameter mutation tool without output schema, the description covers action, ownership, and deactivation behavior. Lacks error handling details but is sufficient for a basic tool.
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 has 100% coverage with a clear description of the id parameter. Description does not add further meaning beyond what the schema already provides.
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 uses specific verb 'Cancel' and resource 'subscription by id', clearly distinguishing it from siblings like subscribe and list_subscriptions. It also adds ownership and deactivation context.
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?
States ownership enforcement ('you can only cancel your own subscriptions'), providing clear context on when the tool is applicable. Missing explicit when-not or alternatives, but the intent is 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.
Each tool targets a distinct purpose: data lookup (ask_pipeworx vs deep_research), entity profiles, comparisons, memory, monitoring, and prediction market analysis. Overlaps are minimal and mitigated by explicit usage guidance (e.g., ask_pipeworx vs. ask_pipeworx_grounded vs. deep_research).
All tools use descriptive snake_case names following a verb_noun or verb_preposition pattern (e.g., entity_profile, resolve_entity, scan_dependency). The naming is predictable and internally consistent, making it easy for an agent to infer tool purposes.
33 tools is on the high end for typical MCP servers. However, the server covers an exceptionally broad domain (structured data across SEC, FDA, FRED, weather, news, crypto, etc.) and includes meta-tools, monitoring, and memory. The count is justified but may feel excessive for many use cases.
The tool surface covers the full lifecycle of data access and analysis: discovery (discover_tools, suggest_questions), retrieval (ask_pipeworx, entity_profile), comparison, claim validation, monitoring, memory, and feedback. There are no obvious gaps for the declared domain, and a feedback tool is provided for missing functionality.