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?
Annotations indicate non-destructive and idempotent. Description adds that the row is deactivated (not deleted) and historical events remain via 'recent_alerts', exceeding annotation coverage. No contradiction.
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 with front-loaded purpose, ownership, and side effect. No wasted 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 single-parameter tool without output schema, the description fully explains the action, ownership constraint, deactivation effect, and links to historical data via sibling tool 'recent_alerts'.
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 description covers the 'id' parameter as a subscription uuid. The description does not add additional semantics beyond what the schema provides, so 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 states 'Cancel a subscription by id' with clear verb-resource pairing. Distinguishes from siblings 'subscribe' and 'list_subscriptions' by specifying the cancel action and deactivation behavior.
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?
Ownership is explicitly enforced ('only cancel your own subscriptions'), providing clear when-to-use context. Does not explicitly state alternatives, but the sibling list implies options like 'list_subscriptions'.
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.
Most tools have distinct roles, but there is meaningful overlap among the question-answering family (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research) and among the Polymarket analysis tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_fill_risk). The long descriptions help separate them, but the boundaries are still subtle enough that an agent could easily pick the wrong variant.
The naming is mostly snake_case and generally follows a verb_noun pattern (ask_pipeworx, compare_entities, resolve_entity, scan_dependency, validate_claim). Deviations like entity_profile, recent_alerts, recent_changes, and bare verbs (forget, recall, remember, subscribe, unsubscribe) are minor and do not seriously harm predictability.
31 tools is heavy for a single server and suggests the surface is a bundled platform (data queries, prediction markets, memory, subscriptions, AI-visibility checks) rather than one tightly scoped domain. Each tool has a rational purpose, but the sheer count plus several meta/didactic tools makes the set feel somewhat oversized.
Core workflows are well covered: entity resolution, profiles, comparisons, grounded lookup, fact-checking, deep research, memory CRUD, and subscription lifecycle. Gaps are minor. There are no update operations for subscriptions, and some optional data sources degrade softly, but agents can accomplish the intended research, monitoring, and memory tasks without dead ends.