Skip to main content
Glama

postedly_checkout_status

Read-onlyIdempotent

Returns the recorded outcome of browser checkout using its original quoteId (checkoutReference). Follows quote renewal and returns the order ID, payment and fulfillment states when available. Read-only; does not create, charge or send.

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": "postedly_checkout_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
quoteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond them: it follows quote renewal, and it explains that order ID, payment and fulfillment states are returned only 'when available', which sets expectations about partial results. The closing 'does not create, charge or send' restates the annotation but usefully clarifies in domain terms.

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, front-loaded with the core action, then the payload, then the safety boundary. No filler or repetition beyond one brief reinforcing clause about not creating or charging.

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?

There is no output schema, and the description compensates by naming what comes back: order ID, payment state and fulfillment state, with the caveat that they may be unavailable. Combined with the annotations covering safety and idempotency, an agent has everything needed to call this correctly.

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?

With a single parameter and 0% schema description coverage, the description carries the burden, and it does: quoteId is clarified as the checkout's original quote reference (checkoutReference), implying the caller must pass the pre-renewal identifier rather than a newer one. That is meaningful guidance the schema type/maxLength cannot convey. It does not cover the length bound or value format, so it is not fully exhaustive.

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 opens with a specific verb-plus-resource: it returns the recorded outcome of a browser checkout, keyed by the original quoteId. That is far more than a restatement of the name. It stops short of naming a sibling (e.g. postedly_quote or postedly_order_status) to contrast against, so the differentiation is implicit rather than explicit.

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?

The phrase 'using its original quoteId (checkoutReference)' implies the appropriate moment: after a browser checkout has occurred, reusing the original reference. There is no explicit when-not guidance and no named alternative for closely related calls such as quote or order status, so the agent must infer the boundary.

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