Skip to main content
Glama

ForthClear Liquidation Marketplace

Get incoming quote requests

get_quote_requests
Read-only

List quote requests buyers sent you. Requires sign-in with seller access. Filter to pending, responded, or all. OAuth discovery: /.well-known/oauth-authorization-server (scope seller:read).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_quote_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoWhich of the calling seller's quote requests to return: pending (awaiting a reply), responded, or all.pending

Output Schema

NameRequiredDescriptionDefault
totalYes
quotesYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / status / description
      Added value: +"Which of the calling seller's quote requests to return: pending (awaiting a reply), responded, or all."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "quotes": {
      +      "items": {
      +        "properties": {
      +          "buyer_company": {
      +            "type": "string"
      +          },
      +          "created_at": {
      +            "description": "ISO-8601 timestamp.",
      +            "type": "string"
      +          },
      +          "id": {
      +            "type": "integer"
      +          },
      +          "message": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "product_id": {
      +            "type": "string"
      +          },
      +          "product_name": {
      +            "type": "string"
      +          },
      +          "quantity": {
      +            "type": "integer"
      +          },
      +          "status": {
      +            "type": "string"
      +          },
      +          "target_price": {
      +            "description": "Buyer target in cents.",
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "product_id",
      +          "quantity",
      +          "status",
      +          "created_at"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "quotes",
      +    "total",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the seller-access authentication requirement and the OAuth discovery endpoint with the seller:read scope. Pagination and ordering behavior are left unstated, though the output schema covers the return shape.

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?

Three short, front-loaded sentences: purpose first, then auth, then filter options. The OAuth discovery line is dense but useful and earns its place. No filler or repetition.

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

Completeness4/5

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

For a read-only list tool with an output schema, the description covers purpose, auth requirements, and filtering adequately. It omits pagination behavior and any indication of result volume or ordering, which would be helpful for an agent deciding whether to page through results.

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%; the single status parameter already has a full enum description with a default. The description's 'Filter to pending, responded, or all' merely restates the schema and adds no new semantics such as default behavior or result ordering.

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?

The description names a specific verb and resource with clear directionality: 'List quote requests buyers sent you' establishes the seller-inbox perspective. It does not explicitly contrast with siblings such as get_quote_status or list_my_quotes, so the boundary is inferred rather than stated.

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?

It gives a prerequisite ('Requires sign-in with seller access') and describes the status filter options, which is useful context. However, it never states when to use this tool versus get_quote_status or seller_inbox_summarise, and provides no 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