Skip to main content
Glama

dns-of-money

by io.github.sparkmastergrape
OverviewDiscussionsAdmin

get_payment_requirements

Get x402 PaymentRequirements for paying a pay: alias. Returns the 402 accepts block (scheme, network, payTo, asset, amount, invoiceId) an x402 agent needs to construct and submit the payment. currency='XRP' settles on the XRP Ledger (amount in drops); currency='USDC' settles USDC on Algorand via the GoPlausible facilitator (amount in atomic micro-USDC, feePayer in extra). The deterministic resolver chooses the rail; this tool never moves money. Example: get_payment_requirements('pay:acme.user', amount='1.5').

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNoAmount to pay — decimal string in the asset's display unit (XRP). Omit it to be quoted the alias's declared price; required for an alias that declares no price.
currencyNoAsset to pay in: 'XRP' (XRPL) or 'USDC' (Algorand). Defaults to XRP.
alias_uriYesThe pay: address to pay. E.g. 'pay:acme.user'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"Amount to pay — decimal string in the asset's display unit (XRP)."New value: +"Amount to pay — decimal string in the asset's display unit (XRP). Omit it to be quoted the alias's declared price; required for an alias that declares no price."
    • changedInput schema / required
      Previous value: -[
-  "alias_uri",
-  "amount"
-]New value: +[
+  "alias_uri"
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Discloses that the tool never moves money and describes deterministic resolver behavior. With no annotations, it adds good context about return fields and currency-specific settlement, but lacks mention of error handling or edge cases.

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 concise and well-structured, with a clear purpose statement upfront, followed by relevant details and an example. No superfluous sentences.

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?

Covers return format, currency details, amount semantics, and includes an example. Lacks error scenarios or behavior for invalid aliases, but overall sufficient for a single-purpose tool.

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?

Adds significant meaning beyond the schema: explains amount omission behavior, currency-specific settlement details, and provides an example. Schema coverage is 100%, but description enhances understanding.

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 the tool retrieves PaymentRequirements for a pay: alias, with a specific verb and resource. It distinguishes from siblings like check_alias_available or resolve_alias by focusing on payment requirements.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage examples and explains when to omit the amount (get quoted price) vs required. However, it does not explicitly state when to use this tool over alternatives or when not to use it.

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

All dns-of-money toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources