Skip to main content
Glama

get_payment_link

Read-onlyIdempotent

Retrieve a payment link's details and status using your reference ID to inspect an order's total, timestamps, and checkout URL.

Instructions

Fetch one payment link by your reference ID, including its current status.

Use this to inspect a single order: status, total, timestamps, checkout url. To
answer "can I deliver yet?", call `check_order_paid` instead — it applies the
paid / safeToFulfil verdict rather than leaving you to interpret the status. For many
orders use `get_payment_links_batch`; to browse without knowing IDs use
`list_payment_links`.

Read-only, no side effects. The checkout `code` is returned only by link creation,
and `lineItem` and `webhookSecret` are never echoed back by any endpoint — this call
cannot recover them. `total` comes back as a string, so parse it before doing
arithmetic, and `env` is absent because Wayl never reports which environment a link
belongs to.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reference_idYesYour own order reference ID, exactly as passed when the link was created. This is not Wayl's internal link `id`.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, idempotentHint), the description adds valuable behavioral specifics: 'Read-only, no side effects,' plus the caveats that checkout `code` is only returned at creation, `lineItem` and `webhookSecret` are never echoed, `total` arrives as a string needing parsing, and `env` is never reported. These are non-obvious traits that help the agent avoid misinterpretation.

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?

The description is front-loaded with the core purpose, then adds compact usage guidance and caveats in four sentences. Every sentence adds relevant information (alternatives, side effects, field behaviors, type gotcha), with no redundancy or fluff.

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?

The tool has one parameter and an output schema, but the description still covers return fields (status, total, timestamps, checkout url) and details which fields are absent. It also covers when to use it vs. siblings, making it complete for an agent to invoke correctly.

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?

The input schema already fully describes `reference_id` (100% coverage) including that it is the user's reference ID and not Wayl's internal link `id`. The description adds little beyond what the schema provides, so the baseline of 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?

The description states 'Fetch one payment link by your reference ID, including its current status,' which is a specific verb+resource. It clearly distinguishes the tool from siblings like check_order_paid, get_payment_links_batch, and list_payment_links by explaining what unique role this tool serves.

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 usage guidance is provided: 'Use this to inspect a single order...' and then directly states when to use alternatives: 'To answer "can I deliver yet?", call check_order_paid instead... For many orders use get_payment_links_batch; to browse without knowing IDs use list_payment_links.' This fully clarifies when to use this tool vs. alternatives.

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/muthanii/waylMCP'

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