Skip to main content
Glama

xrplme_get_country_schema

Standard data for one country: the structured record plus its freshness, at the $1 tier. REQUIRES PAYMENT.
  XRPL   : 1 XRP  via x_payment_signature + x_inv_id
  Solana : $1.00 USDC via x_sol_payload
  Base   : $1.00 USDC via x_base_tx

Args:
    slug: Country slug (e.g., "thailand")
    x_payment_signature: JSON string containing tx_hash AND signedTxBlob
        (hex-encoded signed XRPL tx). Both are required: the t54
        facilitator decodes the blob to bind the on-chain InvoiceID.
    x_inv_id: Invoice ID
    x_sol_payload: OPTIONAL. base64 of an x402 PaymentPayload paying USDC
        on Solana. When present it is verified AND settled via the local
        facilitator; the XRPL arguments are then ignored.
    x_base_tx: OPTIONAL. Hash of your own USDC transfer on Base
        (eip155:8453) to the payTo in the payment_required error. Verified
        on-chain and consumed once; the other arguments are then ignored.

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": {
      "slug": "<slug>"
    },
    "name": "xrplme_get_country_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYes
x_inv_idNo
x_base_txNo
x_sol_payloadNo
x_payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x_base_tx
      Added value: +{
      +  "default": null,
      +  "title": "X Base Tx",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / x_sol_payload
      Added value: +{
      +  "default": null,
      +  "title": "X Sol Payload",
      +  "type": "string"
      +}
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the behavioral burden and does well: it discloses that payment is required, names the accepted payment paths, explains verification/settlement for Solana and Base, notes one-time consumption for Base, and describes argument precedence. It still leaves some behavioral gaps, such as what happens on invalid or failed payment beyond the referenced payment_required error.

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?

The description is front-loaded with purpose and payment requirements, then uses a clear Args block for parameters. It is appropriately sized for a paid five-parameter tool, though some facilitator implementation detail is denser than strictly necessary for invocation.

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?

Given zero annotation coverage, no output schema, and 0% schema description coverage, the description is substantially complete on invocation-critical details: payment, parameter semantics, and argument precedence. Its main gap is that the return value is only summarized as 'structured record plus its freshness' without further detail on shape or freshness format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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 define all five parameters, and it does: slug with an example, x_payment_signature with required internal fields and purpose, x_inv_id as Invoice ID, x_sol_payload as optional base64 x402 payload, and x_base_tx as an optional Base transaction hash. It also explains how optional payment arguments override the XRPL arguments.

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 resource and output: 'Standard data for one country: the structured record plus its freshness, at the $1 tier.' This is clear enough to understand what is returned, but it does not distinguish the tool from siblings such as xrplme_get_country_data or xrplme_get_country_status, and the name's 'schema' wording is not explained.

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 gives detailed conditions for choosing between payment methods, including when XRPL arguments are ignored in favor of x_sol_payload or x_base_tx. However, it provides no explicit guidance on when to use this tool versus sibling country-data tools, nor does it state 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources