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?
Description discloses that the row is deactivated (not deleted) and historical events remain via recent_alerts, adding context beyond annotations which provide idempotent and destructive hints.
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-load the main action and provide essential detail without waste. Every word earns its place.
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 tool with no output schema, the description covers the effect (deactivation vs deletion), ownership constraint, and impact on historical data. No gaps.
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 id parameter already described. The description adds no new meaning beyond 'returned by subscribe', so baseline score 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 clearly states the action 'Cancel a subscription by id' with specific verb and resource, and distinguishes from sibling tools like subscribe and list_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?
The description mentions ownership enforcement ('you can only cancel your own subscriptions'), but lacks explicit guidance on when to use this tool vs alternatives or when not to use it.
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.
Many tools have overlapping purposes, e.g., ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded all route questions to data sources with minor differences. Form D tools and meta-tools (discover_tools, suggest_questions) further blur boundaries, making it hard for an agent to select the right tool.
Most tools follow a consistent snake_case verb_noun pattern (e.g., resolve_entity, validate_claim, subscribe). However, there are minor deviations like bet_research and deep_research without clear verbs, and the ask_pipeworx variants use irregular suffixes.
With 39 tools, the server is over-scoped, including many utility and meta-tools (remember, recall, forget, list_subscriptions) that inflate the count beyond the core domain (SEC Form D and data lookups). A more focused set of 10-15 tools would be more coherent.
The tool set covers a very broad range of data sources and actions, including SEC filings, prediction markets, entity profiling, and AI visibility. However, the completeness is uneven; for example, there are many Form D tools but few for other SEC forms, and some areas like weather or clinical trials are only accessible via ask_pipeworx.