Skip to main content
Glama

respond_rfq

Submit a sealed-bid price quote for an open RFQ. Your quote stays private, and losing bids are never revealed. No funds locked until the requester accepts.

Instructions

Market-maker tool — submit a sealed-bid price quote to compete on an open RFQ. Quotes are private: other makers cannot see your price, and losing bids are never revealed. No funds are locked until the requester accepts a quote.

USE WHEN: the MCP client is acting as a market maker and has decided to quote on a specific open RFQ (obtained via list_open_rfqs). DO NOT USE WHEN: acting as an end-user buyer or seller who wants to receive quotes — use create_rfq instead. This is the market-maker side only; sealed bids, not open negotiation.

PARAM NOTES: price is per unit of base token in quote-token terms (e.g. "3450.00" for ETH priced in USDT). amount is base-token amount offered. No funds are locked at quote time — settlement only begins when the requester accepts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rfqIdYesID of the RFQ to respond to
priceYesPrice per unit of base token in quote token terms (e.g., "3450.00")
amountYesAmount of base token to offer
expiresInNoQuote expiration in seconds
client_request_idNoIdempotency key. Retrying the SAME write with the SAME id within this MCP session returns the first result instead of triggering a second on-chain/backend side effect. Best-effort: not durable across MCP restarts.
Behavior5/5

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

Discloses sealed-bid privacy, no funds locked until acceptance, losing bids not revealed, and idempotency key behavior. No annotations provided, so description fully covers safety and behavior.

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?

Concise, well-organized with USE WHEN, DO NOT USE, PARAM NOTES sections. No redundant information, every sentence adds value.

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?

For a tool with 5 parameters and no output schema, the description covers purpose, usage, parameter details, and behavioral notes comprehensively. No obvious gaps.

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%, baseline 3. Description adds clarifying context: price format with example, amount as base token, and funds-lock semantics for idempotency key. Exceeds baseline.

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?

Clearly states it is a market-maker tool for submitting sealed-bid price quotes on open RFQs. Differentiates from sibling tools like create_rfq and list_open_rfqs.

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

Usage Guidelines5/5

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

Explicit USE WHEN and DO NOT USE conditions, including specific alternatives (create_rfq). Guides agent on correct invocation context.

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/Hashlock-Tech/hashlock-mcp'

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