Skip to main content
Glama

Cancel your RFQ

cancel_rfq
DestructiveIdempotent

Cancel your own RFQ or private order before a deal is agreed so no one can quote or take it. Agreed deals settle or refund through their swap.

Instructions

Cancel your own request or private order so no one can quote or take it. Only before a deal on it is agreed; an agreed deal settles or refunds through its swap.

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": {
      "rfq_id": "<rfq_id>"
    },
    "name": "cancel_rfq"
  }
}

Input Schema

NameRequiredDescriptionDefault
rfq_idYesRequest id (rfqId) from list_open_rfqs, my_rfqs, create_rfq or a share link

Output Schema

NameRequiredDescriptionDefault
errorNoSet instead when the call failed
rfqIdNoRequest id
statusNo
askPriceNoTotal ask; null if none
baseAmountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.11.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / rfq_id / description
      Added value: +"Request id (rfqId) from list_open_rfqs, my_rfqs, create_rfq or a share link"
    • addedInput schema / properties / rfq_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "askPrice": {
      +      "description": "Total ask; null if none",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "baseAmount": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "additionalProperties": {},
      +      "description": "Set instead when the call failed",
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "is_retryable": {
      +          "type": "boolean"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "recovery_hint": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "rfqId": {
      +      "description": "Request id",
      +      "type": "string"
      +    },
      +    "status": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Addedv0.10.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description's added value is the state precondition and the consequence that the RFQ becomes unquotable/unfillable. It stops short of saying what happens to existing quotes or whether cancellation is reversible once executed.

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?

Two short sentences, the action and its effect first, the precondition second. No filler or repetition of schema or annotation content.

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?

With an output schema present and rich annotations, the description only needs to convey preconditions and consequences, which it does. A brief note on what happens to already-submitted quotes would make it fully complete for a destructive single-parameter tool.

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 description coverage is 100% and the single rfq_id parameter already documents its format and provenance (list_open_rfqs, my_rfqs, create_rfq, share link). The description adds no further meaning about the identifier, so the baseline of 3 applies.

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?

States a concrete verb and resource ('Cancel your own request or private order') plus the effect ('so no one can quote or take it'), which makes the outcome unambiguous. The ownership qualifier 'your own' also separates it from any administrative cancellation path implied by the sibling set.

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

Usage Guidelines4/5

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

Gives an explicit precondition ('Only before a deal on it is agreed') and redirects the agreed-deal case to the swap settlement/refund path. The alternative is described as a flow ('its swap') rather than naming the specific sibling tools such as fund_leg or refund_leg, so routing is clear but not fully pinned down.

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