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?
The description discloses important behavioral details beyond the annotations: ownership enforcement and the deactivation (not deletion) behavior. The annotation already indicates destructiveHint=false and idempotentHint=true, but the description adds clarity that the row is deactivated and that historical events stay available via recent_alerts, which is valuable for the agent.
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 concise, information-dense sentences. Each sentence earns its place: the first states the action, the second explains the ownership constraint, and the third clarifies the soft-delete behavior and its consequence. No redundancy or fluff.
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 one-parameter tool with helpful annotations, the description is complete. It explains the cancel operation, the ownership rule, and the impact on historical data. No output schema is present, but the agent can infer a successful cancellation from the idempotent and non-destructive hints. The description fully supports correct invocation.
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 input schema has 100% coverage with a clear description for the single parameter id. The tool description simply reinforces 'by id' without adding new meaning, so the schema is already doing the heavy lifting. No extra parameter semantics are needed.
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.' It uses a specific verb ('Cancel') and resource ('subscription'), and it distinguishes itself from sibling tools like subscribe and list_subscriptions by describing the cancellation behavior and the soft-delete mechanism.
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 implies the appropriate use case (cancelling a subscription) and provides useful context about ownership (only cancel your own) and the fact that historical events remain accessible via recent_alerts. While it does not explicitly mention alternatives or when not to use it, the context is clear and sufficiently guides the agent.
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., multiple ask_pipeworx variants, deep_research, and bet_research all serve data retrieval with subtle differences. The descriptions help distinguish them, but the sheer number of similar tools creates ambiguity.
Tool names are mostly snake_case with a verb_noun pattern (e.g., resolve_entity, validate_claim). A few are nouns like 'readability' or 'text_stats', but the overall style is consistent and readable.
With 33 tools, the server is overstuffed. The server name 'Textstats' suggests a narrow focus, but it covers diverse domains (Polymarket, SEC, memory, subscriptions), making it feel bloated and unfocused.
The tool set covers a wide range of data sources and actions, but there are notable gaps for a 'text stats' server—only two tools directly handle text analysis. Additionally, obvious operations like a simple stock quote tool are missing, relying on ask_pipeworx instead.