Skip to main content
Glama

Get one RFQ

get_rfq
Read-onlyIdempotent

Retrieve a single RFQ or private order by ID to view direction, amounts, assets, ask price, visibility, status, and expiry. Anyone with the ID can read it, enabling shared private order links.

Instructions

One request or private order by id: direction, base amount and asset, quote asset, ask price (null when none was set), visibility, status and expiry. Anyone holding the id can read it, which is how a private order's link works. An unknown id returns an error. To browse use list_open_rfqs; for your own use my_rfqs.

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": "get_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.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real context beyond that: 'Anyone holding the id can read it, which is how a private order's link works' discloses the access model, and 'An unknown id returns an error' discloses failure behavior. It stops short of noting anything about output shape, but an output schema exists, so a 4 is fair.

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?

Front-loaded with purpose and field scope, then access semantics, then error behavior, then sibling routing – a sensible order with no filler sentences. The enumerated field list partly duplicates what the output schema already provides, which is the only wasted weight.

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 single-parameter read tool with rich annotations and an output schema, the description covers purpose, access control, error behavior and alternatives. Nothing an agent needs before calling it is missing.

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 the single parameter already documents uuid format and where the id comes from. The description only says 'by id', adding no syntax, sourcing, or validation detail beyond the schema, so the baseline 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?

Opens with a specific retrieval action and resource: 'One request or private order by id', then enumerates the returned attributes (direction, base amount/asset, quote asset, ask price, visibility, status, expiry). It also names the sibling tools list_open_rfqs and my_rfqs, so an agent can distinguish this fetch-by-id tool from browsing tools without opening any schema.

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?

Explicitly routes the agent: 'To browse use list_open_rfqs; for your own use my_rfqs.' That gives both an alternative and the condition selecting each, which is exactly the when/when-not guidance the dimension asks for.

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