Skip to main content
Glama

ForthClear Liquidation Marketplace

Respond to a quote request

respond_to_quote
Destructive

Answer a quote from a buyer by accepting it, sending a counter-price, or declining. Requires sign-in with seller access. The buyer is notified. OAuth discovery: /.well-known/oauth-authorization-server (scope seller:write). Sensitive: requires user approval each time.

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": {
      "quote_request_id": "<quote_request_id>",
      "action": "<action>"
    },
    "name": "respond_to_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesaccept the buyer's terms as asked, counter with a different price (requires counter_price), or decline the request.
messageNoOptional note sent to the buyer alongside the decision.
counter_priceNoCounter offer price in cents (for counter action)
quote_request_idYesId of the quote request to answer, as returned by get_quote_requests.

Output Schema

NameRequiredDescriptionDefault
quoteYes
messageYes
successYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "quote": {
      +      "properties": {
      +        "action": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "type": "integer"
      +        },
      +        "response_price": {
      +          "type": "integer"
      +        },
      +        "status": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "status",
      +        "action"
      +      ],
      +      "type": "object"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "message",
      +    "quote"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"accept the buyer's terms as asked, counter with a different price (requires counter_price), or decline the request."
    • addedInput schema / properties / message / description
      Added value: +"Optional note sent to the buyer alongside the decision."
    • addedInput schema / properties / quote_request_id / description
      Added value: +"Id of the quote request to answer, as returned by get_quote_requests."
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds meaningful behavior beyond the annotations: seller authentication scope, buyer notification, and a per-call user approval requirement. These details help an agent understand the sensitivity of the mutation, and they are consistent with the destructive/non-idempotent/open-world annotations.

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?

The description is front-loaded with the core action and then supplies only relevant operational details. Authentication, notification, and approval information each earn their place, with no filler.

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 rich input schema, existing output schema, and safety annotations, the description supplies the remaining context an agent needs: seller auth, buyer notification, and required user approval. It is complete for correct invocation without over-explaining values already covered by structured fields.

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 schema already explains the action enum, counter_price, message, and quote_request_id. The description restates the action choices but adds no additional syntax, constraints, or parameter-level meaning beyond what the schema provides.

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?

States a specific verb and resource ('Answer a quote') and enumerates the three actions: accept, counter, decline. It is clear what the tool does, but it does not explicitly distinguish itself from the close sibling accept_quote_and_pay.

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?

Provides an important precondition—seller sign-in access—but does not explicitly say when to use this tool versus alternatives such as accept_quote_and_pay, nor does it state when not to use it. The action choices imply usage but do not provide routing guidance.

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