Skip to main content
Glama

postedly_checkout

Read-onlyIdempotent

Returns a private browser review link for an existing, owned, unexpired quote. Requires only quoteId; viewing the review does not require prior document or terms approval. The review page presents the exact final proof, recipient, total and terms and requires explicit user approval before hosted Stripe Checkout. This operation does not approve, create an order, pay or send.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
quoteIdYes
acceptedTermsNoDeprecated and ignored. Terms acceptance must happen on the browser review page; this field never grants approval.
confirmedDocumentNoDeprecated and ignored. Document approval must happen on the browser review page; this field never grants approval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "https://json-schema.org/draft/2020-12/schema",
      -  "anyOf": [
      -    {
      -      "additionalProperties": false,
      -      "properties": {
      -        "expiresAt": {
      -          "type": "string"
      -        },
      -        "instructions": {
      -          "type": "string"
      -        },
      -        "requiresBrowserApproval": {
      -          "const": true
      -        },
      -        "url": {
      -          "format": "uri",
      -          "type": "string"
      -        }
      -      },
      -      "required": [
      -        "url",
      -        "requiresBrowserApproval",
      -        "expiresAt",
      -        "instructions"
      -      ],
      -      "type": "object"
      -    },
      -    {
      -      "additionalProperties": false,
      -      "properties": {
      -        "error": {
      -          "additionalProperties": false,
      -          "properties": {
      -            "code": {
      -              "minLength": 1,
      -              "type": "string"
      -            },
      -            "details": {
      -              "additionalProperties": false,
      -              "properties": {
      -                "addressRole": {
      -                  "enum": [
      -                    "recipient",
      -                    "sender"
      -                  ]
      -                },
      -                "canSendAsEntered": {
      -                  "type": "boolean"
      -                }
      -              },
      -              "required": [
      -                "addressRole",
      -                "canSendAsEntered"
      -              ],
      -              "type": "object"
      -            },
      -            "message": {
      -              "type": "string"
      -            }
      -          },
      -          "required": [
      -            "code",
      -            "message"
      -          ],
      -          "type": "object"
      -        }
      -      },
      -      "required": [
      -        "error"
      -      ],
      -      "type": "object"
      -    }
      -  ],
      -  "type": "object"
      -}New value: +null
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "expiresAt": {
      +          "type": "string"
      +        },
      +        "instructions": {
      +          "type": "string"
      +        },
      +        "requiresBrowserApproval": {
      +          "const": true
      +        },
      +        "url": {
      +          "format": "uri",
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "url",
      +        "requiresBrowserApproval",
      +        "expiresAt",
      +        "instructions"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "error": {
      +          "additionalProperties": false,
      +          "properties": {
      +            "code": {
      +              "minLength": 1,
      +              "type": "string"
      +            },
      +            "details": {
      +              "additionalProperties": false,
      +              "properties": {
      +                "addressRole": {
      +                  "enum": [
      +                    "recipient",
      +                    "sender"
      +                  ]
      +                },
      +                "canSendAsEntered": {
      +                  "type": "boolean"
      +                }
      +              },
      +              "required": [
      +                "addressRole",
      +                "canSendAsEntered"
      +              ],
      +              "type": "object"
      +            },
      +            "message": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "code",
      +            "message"
      +          ],
      +          "type": "object"
      +        }
      +      },
      +      "required": [
      +        "error"
      +      ],
      +      "type": "object"
      +    }
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds meaningful context: the review page presents 'the exact final proof, recipient, total and terms,' requires explicit user approval before hosted Stripe Checkout, and the deprecated boolean fields are ignored and 'never grant approval.' No contradiction with annotations.

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 dense sentences with no filler. The main purpose is front-loaded, the behavioral caveats are in the middle, and the exclusions close it. Every sentence earns its place.

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 3-parameter tool with rich annotations and no output schema, the description is complete: prerequisites, return value (a private browser review link), page behavior, approval flow, and non-effects are all covered. An agent can invoke it correctly without further information.

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 67%: the deprecated booleans have descriptions, but quoteId only has minLength. The description compensates by explaining quoteId must reference an existing/owned/unexpired quote, that only it is required, and that the deprecated fields are ignored. It adds real meaning beyond the schema.

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?

The description states a specific verb and resource: 'Returns a private browser review link for an existing, owned, unexpired quote.' It also explicitly lists what the operation does not do ('does not approve, create an order, pay or send'), which distinguishes it from siblings like postedly_quote or postedly_orders.

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?

The description gives clear preconditions: the quote must be existing, owned, and unexpired, and only quoteId is required. It also clarifies that no prior document or terms approval is needed for viewing, and lists exclusions. However, it does not explicitly name alternative sibling tools, so it stops short of the highest standard.

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