Skip to main content
Glama

Trusteed Agentic Commerce

by xyz.trusteed
OverviewDiscussionsAdmin

quote_checkout

Read-onlyIdempotent

Read-only price quote. Does not advance the session, open approvals or enable payment. To pay, call preview_checkout.

Computes the same totals as preview_checkout for this cart (subtotal, shipping, discount, tax status, total_is_final), with status QUOTE_ONLY, but not the same checks: it does not check your payment mandate's spending cap; preview_checkout does. Read-only on Trusteed's side: where the store prices orders on its own platform (WooCommerce), the store builds a temporary cart to compute the quote and discards it. Checkout guide: read the MCP resource trusteed://guides/checkout.

Input Schema

NameRequiredDescriptionDefault
cart_idYesCart session ID returned by create_cart
agent_keyNoSandbox credential from `create_sandbox_key`. Use this when your client cannot set an `Authorization: Bearer` header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": true,
-  "properties": {
-    "checkout_session_id": {
-      "type": "string"
-    },
-    "currency": {
-      "type": "string"
-    },
-    "discount_cents": {
-      "type": "number"
-    },
-    "expires_at": {
-      "description": "ISO-8601 UTC instant at which this checkout SESSION stops being usable. It is not a stock reservation and not a price guarantee.",
-      "type": "string"
-    },
-    "expires_in_seconds": {
-      "description": "Whole seconds left on this checkout SESSION at response time (0 when already past). It is not a stock reservation and not a price guarantee.",
-      "minimum": 0,
-      "type": "integer"
-    },
-    "items": {
-      "items": {
-        "additionalProperties": true,
-        "properties": {
-          "line_price": {
-            "type": "number"
-          },
-          "name": {
-            "type": "string"
-          },
-          "quantity": {
-            "type": "number"
-          }
-        },
-        "required": [
-          "name",
-          "quantity",
-          "line_price"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    },
-    "quote_only": {
-      "const": true,
-      "type": "boolean"
-    },
-    "shipping_authoritative": {
-      "type": "boolean"
-    },
-    "shipping_cents": {
-      "type": "number"
-    },
-    "shipping_source": {
-      "enum": [
-        "platform",
-        "merchant_policy",
-        "estimated"
-      ],
-      "type": "string"
-    },
-    "shipping_title": {
-      "type": "string"
-    },
-    "status": {
-      "const": "QUOTE_ONLY",
-      "type": "string"
-    },
-    "store_name": {
-      "type": "string"
-    },
-    "subtotal_cents": {
-      "type": "number"
-    },
-    "tax_cents": {
-      "type": "number"
-    },
-    "tax_status": {
-      "enum": [
-        "included",
-        "not_calculated"
-      ],
-      "type": "string"
-    },
-    "total_cents": {
-      "type": "number"
-    },
-    "total_is_final": {
-      "type": "boolean"
-    },
-    "total_note": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "checkout_session_id",
-    "store_name",
-    "items",
-    "subtotal_cents",
-    "shipping_cents",
-    "discount_cents",
-    "total_cents",
-    "currency",
-    "tax_cents",
-    "tax_status",
-    "total_is_final",
-    "total_note",
-    "status",
-    "quote_only"
-  ],
-  "type": "object"
-}New value: +null
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds substantial non-obvious context: no session advancement, no approvals, no payment enablement, no spending-cap enforcement, and the fact that WooCommerce stores build and discard a temporary cart. This is exactly the extra behavioral disclosure the dimension rewards.

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?

Front-loads the core definition and the routing alternative in the first two sentences. The remaining detail (check differences, WooCommerce internals, guide link) is useful but slightly dense; nearly every sentence earns its place, though the parenthetical total list borders on schema restatement.

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?

With no output schema, the description helpfully enumerates the computed fields (subtotal, shipping, discount, tax status, total_is_final) and the QUOTE_ONLY status, and points to the checkout guide resource. Nothing needed to call or interpret the tool is missing.

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 both parameters (cart_id, agent_key) are fully documented in the schema. The description adds no parameter-level syntax, format, or constraint detail, so the baseline 3 applies.

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 ('Read-only price quote') and immediately distinguishes itself from its closest sibling by naming preview_checkout as the tool that actually enables payment. An agent can route correctly without opening either schema.

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

Usage Guidelines5/5

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

Explicit when-to-use ('read-only price quote') and when-not ('does not advance the session, open approvals or enable payment'), with a named alternative ('To pay, call preview_checkout'). It even specifies a behavioral difference in checks: quote_checkout does not enforce the payment mandate's spending cap while preview_checkout does.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Trusteed Agentic Commerce toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources