Skip to main content
Glama

Get payment link

get_payment_link
Read-onlyIdempotent

Get the secure opas.world link to pay for one of the client's unpaid bookings.

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": {
      "booking_id": "<booking_id>"
    },
    "name": "get_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the link is external (opas.world) and payment-oriented, but says nothing about link expiry, reuse, or behavior for a booking that is already paid or not the caller's.

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?

A single sentence with zero filler, front-loading the action and the concrete resource. Nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool whose annotations already carry the safety and idempotency profile, the description is nearly adequate, but the error/precondition behavior (already paid, wrong owner, expired link) is left entirely unspecified.

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 0% – booking_id carries only type/format, no prose. The description partly compensates by implying the identifier must reference one of the client's unpaid bookings, but it doesn't state the expected outcome for an invalid, foreign, or settled booking.

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?

States a specific verb and resource ("Get the secure opas.world link") plus the scoped object ("one of the client's unpaid bookings"), which no sibling tool plausibly covers. It stops short of naming or contrasting any sibling, so differentiation is inferred rather than stated.

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 "unpaid bookings" implies a precondition for use, but the description never says when to call this instead of alternatives such as get_my_booking or create_booking, nor what to do if the booking is already paid. Usage context is implied rather than given.

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