Skip to main content
Glama

Quote an RFQ

respond_to_rfq
Destructive

Submit a total quote-asset amount to an open RFQ to open a private deal thread; returns a threadId for negotiation and deal-status checks.

Instructions

Respond to an open RFQ with your price. Opens a private deal thread with the creator; returns the threadId for negotiate/deal_status. price = TOTAL quote-asset amount for the whole base amount (not per-unit). Your quote is your acceptance of that price (as the initiator, this tool accepts it for you with your hashlock): when the creator accepts it, the deal is agreed.

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>",
      "price": "<price>"
    },
    "name": "respond_to_rfq"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceYesTotal quote-asset amount, human decimal, at most 8 decimals of its asset (fewer if the asset has fewer); the API refuses more
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
agreedNo
statusNo
swapIdNoSet once agreed
threadIdNoDeal thread id
next_stepNo
next_stepsNo
waiting_forNo
youAcceptedNoThis side accepted currentPrice
currentPriceNoTotal price on the table
pendingPriceNoCounter awaiting acceptance
accept_failedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.11.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / price / description
      Previous value: -"Total quote-asset amount, human decimal"New value: +"Total quote-asset amount, human decimal, at most 8 decimals of its asset (fewer if the asset has fewer); the API refuses more"
    • 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": {
      +    "accept_failed": {
      +      "type": "string"
      +    },
      +    "agreed": {
      +      "type": "boolean"
      +    },
      +    "currentPrice": {
      +      "description": "Total price on the table",
      +      "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"
      +    },
      +    "next_step": {
      +      "type": "string"
      +    },
      +    "next_steps": {
      +      "type": "string"
      +    },
      +    "pendingPrice": {
      +      "description": "Counter awaiting acceptance",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "swapId": {
      +      "description": "Set once agreed",
      +      "type": "string"
      +    },
      +    "threadId": {
      +      "description": "Deal thread id",
      +      "type": "string"
      +    },
      +    "waiting_for": {
      +      "type": "string"
      +    },
      +    "youAccepted": {
      +      "description": "This side accepted currentPrice",
      +      "type": "boolean"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Addedv0.10.0

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the key behavioral traits: it opens a private deal thread, returns a threadId usable by negotiate/deal_status, commits the initiator's price via hashlock, and completes only when the creator accepts. This meaningfully explains the destructive/commitment semantics that annotations alone (destructiveHint=true, idempotentHint=false) only flag without explaining.

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 dense but front-loaded with the action and outcome, and each sentence carries useful information about price semantics, return value, and deal commitment. It could be marginally tighter, but there is no filler or repetition.

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

Completeness5/5

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

Given the tool's complexity (deal thread creation, price commitment, hashlock acceptance) and the existence of an output schema, the description covers what an agent needs to call it correctly: required inputs are implied by the schema, price semantics are clarified, and the consequence of calling it is explained. No critical prerequisite or behavioral context appears missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about the price parameter: it is the TOTAL quote-asset amount for the whole base amount, explicitly not per-unit. That disambiguates a common and costly mistake beyond what the schema text conveys.

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 states a specific verb and resource ('Respond to an open RFQ with your price') and immediately names the concrete effect (opens a private deal thread) and the return value (threadId). It also distinguishes itself from siblings by naming negotiate and deal_status as the follow-on tools, so an agent can differentiate it from create_rfq or get_rfq without opening schemas.

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?

Usage is clearly scoped to 'an open RFQ' and the commitment semantics (your quote is your acceptance) tell the agent this is a binding action rather than exploration. It does not explicitly state when not to use it or name an alternative for non-committal exploration, but the context is strong enough to guide selection.

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