Skip to main content
Glama

marketplace_cancel_subscription

Cancel a tool subscription by providing its ID and your wallet address. Decide between immediate or end-of-period cancellation, optionally adding a reason, to prevent further charges.

Instructions

Cancel your subscription for a tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNoReason for cancellation
immediateNoCancel immediately or at end of period
userAddressYesYour wallet address
subscriptionIdYesThe subscription ID to cancel
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states the action without revealing whether cancellation is irreversible, requires specific authorization, triggers refunds, or how the 'immediate' parameter affects the outcome. This is a significant gap for a mutating operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that communicates the core purpose without unnecessary words. However, it omits useful context that could be added without bloating, so it earns a 4 rather than a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a cancellation tool with no annotations and no output schema, the description is incomplete. It does not explain the difference between immediate and end-of-period cancellation, the effect on the subscription, or any side effects. The tool likely has significant implications that the description fails to address.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already provides descriptions for all four parameters (100% coverage), including the 'immediate' flag and 'reason' field. The description adds no additional meaning about how parameters interact or should be used, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Cancel your subscription for a tool' clearly states the action (cancel) and the target (subscription for a tool). It distinguishes itself from sibling marketplace management tools like pause, activate, or update by using the specific verb 'cancel'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no guidance on when to use this tool versus alternatives. It does not mention that pausing is an alternative, nor does it explain when to use immediate cancellation versus end-of-period. There is no context about prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nirholas/universal-crypto-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server