Skip to main content
Glama

accept_commerce_quote

accept_commerce_quote

Buyer: accept a quote and create an order. Requires authentication.

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": {
      "quoteId": "<quoteId>"
    },
    "name": "accept_commerce_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYesQuote id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose two important traits: authentication is required and the call is a mutation that creates an order. It omits what happens on an expired or already-accepted quote, whether the operation is idempotent, and what the caller receives.

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?

Two short sentences with the mutation and the auth requirement front-loaded and no filler. The leading "Buyer:" fragment is slightly terse but still readable.

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

Completeness3/5

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

For a one-parameter mutating tool with no annotations and no output schema, the definition covers the essentials of who and what, but leaves failure modes and the return value unaddressed. An agent could call it correctly but not predict its errors.

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?

Only one parameter, quoteId, and schema description coverage is 100%, so the schema already defines it fully. The description adds no format, source, or validation meaning beyond that baseline.

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 ("accept a quote") plus the resulting side effect ("create an order"), which lets an agent distinguish it from quote-creation or order-completion siblings. It stops short of naming an alternative explicitly, so differentiation relies on inference.

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?

"Buyer:" signals the acting role, which is useful routing context, but there is no statement of when to use this versus create_commerce_quote or complete_commerce_order, and no preconditions such as the quote being open or unexpired.

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