Skip to main content
Glama

call_paid_service

Invoke any Glitter Agent Gate endpoint by service slug and sub-path to get status, result, and XRP/RLUSD x402 payment details; without a wallet, receive a quote and no charge.

Instructions

Generic caller for any Glitter Agent Gate endpoint (own tools or listed providers) by service slug and sub-path. Returns {status, http, result, payment:{asset, amount, tx, explorer}}. Paid per call with x402 from your XRPL_SEED wallet (XRP or RLUSD, capped by MAX_*PER_CALL and SESSION_BUDGET*). Without a wallet it returns the price quote and charges nothing. Failed calls are not charged.

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": {
      "service": "<service>"
    },
    "name": "call_paid_service"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON body for POST endpoints
pathNoSub-path, e.g. "/account"
assetNoAsset to pay with on the XRP Ledger: XRP (default) or RLUSD
queryNoQuery parameters
methodNo
serviceYesService slug from list_services, e.g. xrpl-data

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior5/5

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

With no annotations, the description carries the burden and does so well: it discloses the return shape ({status, http, result, payment:{asset, amount, tx, explorer}}), the x402 payment mechanism and its source wallet, the budget caps (MAX_*_PER_CALL, SESSION_BUDGET_*), and two critical edge cases – no wallet means a quote with no charge, and failed calls are not charged. That is exactly the behavior an agent needs before triggering a paid mutation.

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?

Four dense sentences with the core purpose front-loaded and the return shape placed before the payment mechanics. Some parenthetical jargon (MAX_*_PER_CALL, x402) is underexplained, but no sentence is filler.

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 six-parameter paid gateway tool with no annotations and no output schema, the description covers return shape, payment, failure charging, and the no-wallet path – a lot. Gaps remain on invalid-slug behavior and the default for method (the schema lists GET/POST without a default), so it is not fully complete.

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?

Schema coverage is 83%, so the baseline is 3, but the description adds real meaning to the payment-related parameters: asset is tied to the XRPL wallet and XRP/RLUSD budget caps, and service is clarified as a slug of an endpoint rather than an arbitrary string. It says little about method, query, or body beyond the schema, keeping it from a 5.

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 gives a specific verb and resource ('generic caller for any Glitter Agent Gate endpoint ... by service slug and sub-path') and names the framing that separates it from narrow siblings: it is the catch-all gateway, while crypto_prices or xrpl_account_info are specific tools. It stops short of explicitly contrasting with those siblings, so it does not fully earn a 5.

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?

It implies usage through the payment flow and notes that without a wallet the call returns a quote instead of charging, which is a genuine when-this-happens condition. However, there is no explicit 'use this when the dedicated tool does not cover X' guidance or exclusion against siblings like crypto_prices, so the agent must infer the routing.

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