Skip to main content
Glama

Loyal Spark Holder

Cancel P2P Offer

cancel_p2p_offer
Destructive

Cancel a P2P offer you created before it is accepted.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "offer_id": "<offer_id>"
    },
    "name": "cancel_p2p_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesP2P offer UUID to cancel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is known. The description adds genuinely new behavioral context: the operation is scoped to your own offers and is only valid pre-acceptance, which an agent cannot derive from the annotations. It does not say what happens to any escrowed assets or how an already-accepted offer is rejected, which keeps it from a 5.

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

Conciseness5/5

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

A single sentence with the resource identified first and the two binding constraints attached. Nothing is redundant and nothing is buried.

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

Completeness4/5

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

For a one-parameter, non-idempotent destructive call with full annotation coverage and no output schema, the definition covers identity, ownership and timing. The remaining gap is outcome disclosure — whether cancellation is final and what happens to held funds — which would matter for a destructive operation but is a modest omission.

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?

Schema coverage is 100% and offer_id is fully documented in the schema as a UUID, so the description carries little extra burden. The phrase 'offer you created' adds an ownership constraint on which UUID is valid, but no format or sourcing details beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

The description pairs a specific verb (cancel) with a specific resource (P2P offer) and adds a scope qualifier: only offers 'you created' and only 'before it is accepted'. That distinguishes it clearly from accept_p2p_offer, create_p2p_offer and list_p2p_offers. It stops short of naming a sibling alternative explicitly, so it is not a 5.

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

Usage Guidelines3/5

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

The state precondition ('before it is accepted') implicitly tells the agent when this tool applies and when it does not (offers already taken cannot be cancelled here). There is no explicit pointer to what to do otherwise, no mention of an alternative tool for post-acceptance situations, and no stated failure behavior.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources