Skip to main content
Glama

xrplme_entity_ownership

Ownership chain for an entity: the chain up to the ultimate parent, plus
its direct subsidiaries. $5.00 per request. Get the ID from
xrplme_entity_lookup first.
  XRPL   : 5 XRP  via x_payment_signature + x_inv_id
  Solana : $5.00 USDC via x_sol_payload
  Base   : $5.00 USDC via x_base_tx

Args:
    entity_id: The 20-character entity ID returned by xrplme_entity_lookup.

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": {
      "entity_id": "<entity_id>"
    },
    "name": "xrplme_entity_ownership"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_inv_idNo
entity_idYes
x_base_txNo
x_sol_payloadNo
x_payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does disclose the important traits: cost ($5.00 per request) and the payment rail per chain (5 XRP via x_payment_signature + x_inv_id, Solana USDC via x_sol_payload, Base USDC via x_base_tx). It does not say whether the call is read-only, whether payment is settled before or after retrieval, what happens on insufficient payment, or what the response contains.

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?

Purpose is front-loaded, followed by pricing, then payment mechanics, then args — a sensible order with little wasted text. The 'Args:' block repeats what the payment lines already implied and the indented payment notation is terse enough to be slightly cryptic.

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 paid, multi-chain tool with no annotations and no output schema, the definition covers cost, payment inputs, and the lookup prerequisite, which is the critical path. It is still incomplete on the return value — 'ownership chain' is never described in terms of fields or shape despite there being no output schema — and on failure modes.

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 0%, so the description must compensate, and it largely does: entity_id is explained as a 20-character ID obtained from xrplme_entity_lookup, and the four x_ parameters are mapped to their respective chains. It never states that the payment parameters are optional/nullable or that exactly one payment set applies per request, which leaves a real ambiguity.

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 opening sentence states a specific resource and scope: the ownership chain up to the ultimate parent plus direct subsidiaries. That is enough to distinguish it from xrplme_entity_lookup, which is named as the source of the ID, and from the unrelated country/survey siblings.

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?

It gives an explicit prerequisite ('Get the ID from xrplme_entity_lookup first'), which routes the agent correctly between the two entity tools. It stops short of stating when-not to use it or what to do if the entity has no parent, so it is clear context rather than full when/when-not guidance.

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.