Skip to main content
Glama

ForthClear Liquidation Marketplace

Get quote status

get_quote_status
Read-only

Check a quote you requested: pending, responded, accepted, rejected, or completed, plus the seller price and shipping once they reply. No sign-in required when you pass the status_token from request_quote. Signed-in buyers can also read their own quotes without the token.

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_id": "<quote_id>"
    },
    "name": "get_quote_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYesQuote id from request_quote
status_tokenNostatus_token from the request_quote response

Output Schema

NameRequiredDescriptionDefault
statusYes
quantityYes
quote_idYes
created_atYes
product_idYes
updated_atYes
next_actionYes
buyer_quote_urlYes
seller_responseYes
target_price_per_unitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "buyer_quote_url": {
      +      "type": "string"
      +    },
      +    "created_at": {
      +      "type": "string"
      +    },
      +    "next_action": {
      +      "type": "string"
      +    },
      +    "product_id": {
      +      "type": "string"
      +    },
      +    "quantity": {
      +      "type": "integer"
      +    },
      +    "quote_id": {
      +      "type": "integer"
      +    },
      +    "seller_response": {
      +      "properties": {
      +        "currency": {
      +          "type": "string"
      +        },
      +        "message": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "price_per_unit": {
      +          "type": "number"
      +        },
      +        "shipping": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "total_additional_costs": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        }
      +      },
      +      "required": [
      +        "price_per_unit",
      +        "currency"
      +      ],
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "type": "string"
      +    },
      +    "target_price_per_unit": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "updated_at": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "quote_id",
      +    "product_id",
      +    "quantity",
      +    "status",
      +    "seller_response",
      +    "created_at",
      +    "updated_at",
      +    "next_action",
      +    "buyer_quote_url"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful context beyond that: no sign-in is required when a status_token is supplied, and seller price and shipping appear only after the seller replies. It doesn't mention rate limits or error behavior for invalid/expired tokens, keeping it from a 5.

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?

Three tight sentences: the first front-loads what is returned, the second and third cover the auth model. No filler or repetition of the title.

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 two-parameter read-only lookup with an output schema, the description covers purpose, states, auth modes, and the conditional availability of price/shipping. Return-value detail is rightly left to the output schema.

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 both parameters are already documented. The description still adds real meaning by explaining that status_token is what grants token-based (unauthenticated) access and that quote_id comes from request_quote, clarifying the relationship between the two parameters.

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 specific verb and resource (check a quote) and enumerates the possible states (pending, responded, accepted, rejected, completed) plus the data returned on reply. This is distinguishable from sibling list tools like get_quote_requests and list_my_quotes, which deal with quote collections rather than a single quote's status.

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?

Explains the two access paths clearly: pass status_token from request_quote for unauthenticated access, or be a signed-in buyer reading your own quote. It doesn't explicitly rule out or point to sibling tools (e.g. when to use get_quote_requests instead), so it stops short of full when/when-not 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