Skip to main content
Glama

create_commerce_quote

create_commerce_quote

Seller: create a structured quote for a service. Returns a terms hash. 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": {
      "serviceId": "<serviceId>",
      "buyer": "<buyer>",
      "scope": "<scope>"
    },
    "name": "create_commerce_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
buyerYesBuyer wallet address.
scopeYesWhat will be delivered.
termsNoOptional refund, dispute and SLA terms.
amountUsdNoOptional negotiated amount.
serviceIdYesService listing id.
deliveryDueNoOptional ISO delivery deadline.
expiresInSecondsNoQuote validity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/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; it does add two useful facts beyond the schema — the call requires authentication and it returns a terms hash. It omits whether the quote is recorded on-chain, what happens when expiresInSeconds lapses, whether creation costs gas, and whether the quote is mutable, which are significant gaps for a no-annotation mutation tool.

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 short sentences, zero filler, with the actor role and action front-loaded before the return value and the auth requirement. Nothing is redundant or padded.

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 seven-parameter mutation tool with nested terms and no annotations or output schema, the description gives the auth requirement and the return value but leaves prerequisites (must the seller own the serviceId?), failure modes, and the follow-up accept step unexplained. Adequate as a minimum, but an agent could still invoke it with wrong expectations.

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% with seven well-documented parameters, so the schema already supplies the meaning and the baseline is 3. The description adds no syntax, defaults, or units beyond what the schema states (e.g., it never explains the relationship between terms, amountUsd, and deliveryDue).

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 states a specific verb and resource ('create a structured quote for a service') and names the acting role ('Seller'), so the agent knows exactly what is produced. It does not distinguish this from siblings such as create_invoice or get_payment_quote, so the agent must infer the boundary from the name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no mention of the obvious downstream counterpart (accept_commerce_quote) or how this differs from create_invoice/get_payment_quote. The 'Seller:' prefix hints at the caller role but does not tell the agent when to choose this tool.

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