Skip to main content
Glama

Create a payment link

create_payment_link

Generate a shareable payment link for a crypto invoice, letting the payer open it and pay the specified amount in their own wallet via the configured Request Network route.

Instructions

Bill someone and get a link they can open to pay in their own wallet. Uses the network and token of the receiving route set up in the Request Network dashboard (REQUEST_DESTINATION_ID). The amount is in that route's token. This is the easiest way to get paid.

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": {
      "amount": "<amount>"
    },
    "name": "create_payment_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context — that the network and token are inherited from an externally configured receiving route (REQUEST_DESTINATION_ID) rather than chosen per call, which is something the agent could not derive from the schema. It stops short of saying each call produces a new, non-idempotent link or whether links expire.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and the outcome, with no redundant restatement of the title. The closing 'easiest way to get paid' leans promotional but still carries a routing hint, so it earns most of its place.

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

Completeness4/5

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

For a one-parameter creation tool with annotations covering the safety profile, the description supplies the two things the structured fields omit: what causes the network/token selection and what the caller receives (a payable link). Remaining gaps — link lifetime and whether a persistent record is created — are minor for a tool this simple and with no output schema to explain.

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 description coverage is 0%, so the description must carry the burden for the single `amount` parameter. It does add a crucial semantic point — the amount is denominated in the route's token, not fiat — but says nothing about string precision, formatting, or bounds, leaving the regex pattern in the schema as the only formatting guidance.

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 states a specific verb+resource pair ('Bill someone and get a link they can open to pay') that is clearly distinct from create_invoice, which the wording implicitly contrasts by emphasizing a payable link rather than an invoice document. It does not name the sibling tools directly, so the differentiation is conveyed by concept rather than by explicit routing.

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?

'This is the easiest way to get paid' gives an implied usage preference, but there is no explicit when-to-use/when-not-to-use guidance and no mention of create_invoice as the alternative when a formal invoice is needed. The agent must infer routing from concepts rather than from stated conditions.

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