Skip to main content
Glama

xrplme_entity_lookup

Company look-up: legal name, status, jurisdiction, addresses, registration
date and the permanent entity ID. $1.00 per request.
  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:
    query: Company name, or a 20-character entity ID for an exact hit.
    limit: OPTIONAL. Maximum results for a name search, 1-10, default 5.

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": {
      "query": "<query>"
    },
    "name": "xrplme_entity_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
x_inv_idNo
x_base_txNo
x_sol_payloadNo
x_payment_signatureNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the most important economics — $1.00 per request with the per-chain payment mechanism (1 XRP via x_payment_signature + x_inv_id, USDC on Solana via x_sol_payload, USDC on Base via x_base_tx) — which is genuinely useful. However, it is silent on what happens when payment is missing or invalid, whether failures are still charged, and any rate limits or result cardinality behavior.

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 definition is front-loaded with purpose, then price, then payment mechanics, then arguments — a sensible order with no filler. The terse bullet formatting and indentation are slightly rough but cost nothing in comprehension.

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 paid, six-parameter tool with no annotations and no output schema, the description supplies what the agent actually needs: what is returned, what search modes exist, and how to pay on each supported chain. Remaining gaps are secondary — error/payment-failure semantics and how the four payment parameters interact with the choice of chain.

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 description coverage is 0%, so the description must do the work, and it largely does: query is explained as either a company name or a 20-character entity ID, limit is given its range and default (1-10, default 5), and each of the four payment parameters is mapped to the chain it serves. The only gap is that the description does not state that the payment parameters are conditionally required depending on the chosen chain.

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 opens with a specific verb+resource ('Company look-up') and enumerates the exact fields returned: legal name, status, jurisdiction, addresses, registration date and permanent entity ID. This is unambiguous about what the tool does, but it never distinguishes itself from the closely related sibling 'xrplme_entity_ownership', leaving the agent to infer the boundary.

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?

Usage is only implied through the parameter notes: a company name performs a search, while a 20-character entity ID gives an exact hit. There is no statement of when to prefer this over sibling tools such as entity_ownership or screen, and no prerequisite or exclusion 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.