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 traits beyond the annotations: ownership enforcement, deactivation instead of deletion, and preservation of historical events via recent_alerts. This adds significant context while remaining consistent with the annotations (e.g., destructiveHint=false).
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 tight sentences, each adding value: the action, the ownership constraint, and the deactivation behavior. No waste, front-loaded with the main purpose.
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 mutation tool with no output schema, the description fully covers what the tool does, its constraints, and its downstream effect on recent_alerts. It is complete and self-contained.
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 already fully describes the sole parameter 'id' as 'Subscription id (uuid) returned by subscribe.' The description does not add new meaning beyond referring to the same id, so the baseline of 3 applies for high schema coverage.
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') and the resource ('subscription'), distinguishing it from sibling tools like subscribe and list_subscriptions. The verb 'cancel' is specific and the subject is unambiguous.
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?
It provides a key usage condition ('you can only cancel your own subscriptions') and implies the tool is for canceling subscriptions, but does not explicitly mention alternatives or when to prefer another tool (e.g., list_subscriptions before canceling). This is clear context without exclusions.
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.
The tool set is a chaotic mix of unrelated domains: Oregon Open Data tools (datasets, metadata, query) are buried among dozens of tools for Pipeworx general query, Polymarket betting, memory management, and AI visibility. Many tools have overlapping purposes (e.g., ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) making it impossible for an agent to distinguish the right tool for a given task without deep inspection.
Naming is wildly inconsistent: snake_case (ai_visibility_check, pipeworx_feedback), camelCase (bet_research, datasets, metadata, query), mixed (ask_pipeworx_grounded, polymarket_arbitrage). No consistent verb_noun or pattern exists, and many names are vague (remember, recall, forget) without connection to the server's assumed domain.
33 tools is excessive for a server ostensibly about Oregon Open Data, which only has 3 relevant tools. The remaining 30 are from other services (Pipeworx, Polymarket, etc.) and do not belong, making the count inappropriate for the server's declared purpose.
For the Oregon Open Data domain, the surface is bare: only search, metadata, and query. Missing operations like upload, update, or delete datasets. The heavy presence of unrelated tools (betting, memory, AI visibility) does not compensate for the gap in the actual domain coverage.