Skip to main content
Glama

Get checkout

get_checkout
Read-only

Retrieve checkout details by ID for owner view. Requires merchant read scope.

Instructions

Fetch a checkout by id (owner view). Requires scope merchant_read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
checkout_idYesCheckout id (chk_…).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
amountYes
statusYes
is_liveYes
metadataYesMerchant metadata, parsed to an object when it was valid JSON.
image_urlYes
created_atYes
expires_atYes
approved_atYes
descriptionYes
pix_payloadYesPIX payload; present only while pending.
callback_urlYes
cancelled_atYes
completed_atYes
redirect_urlYes
processing_atYes
blockchain_tx_idYes
rejection_reasonsYesProvider reason codes when the underlying payment was refused/held; [] otherwise.
Behavior4/5

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

Beyond readOnlyHint and openWorldHint annotations, the description adds the scope requirement and owner view, providing useful behavioral context.

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?

One sentence, directly front-loading the purpose with no wasted words.

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 a single parameter and output schema present, the description is complete for the tool's simplicity.

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 coverage is 100%, and the description does not expand on the parameter beyond what the schema provides. Baseline score 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?

The description clearly states it fetches a checkout by ID with owner view, distinguishing from sibling tools like list_checkouts.

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 description lacks explicit guidance on when to use vs alternatives, though the scope requirement is stated. No when-not-to-use info.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/depixapp/depix-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server