Skip to main content
Glama

xrplme_screen

Screening check for a person or a company, before you deal with them.
Returns matches with the programme, designation date and a citation.
$2.00 per check.
  XRPL   : 2 XRP  via x_payment_signature + x_inv_id
  Solana : $2.00 USDC via x_sol_payload
  Base   : $2.00 USDC via x_base_tx

Args:
    name: Person or company name to check (at least 2 characters).
    type: OPTIONAL. "individual" or "entity" to narrow the match.
    country: OPTIONAL. Two-letter country filter.
    limit: OPTIONAL. Maximum results, 1-25, default 10.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
typeNo
limitNo
countryNo
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
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose substantial behavior: a $2.00 charge per call, the three accepted payment rails with their respective parameters, and the shape of the result (matches with programme, designation date, citation). It does not say whether payment is mandatory before results are returned, nor what a no-match or unpaid response looks like, which keeps it from a 5.

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 and return shape are front-loaded, followed by pricing and payment rails, then argument notes — a logical order with little filler. The args block partially restates schema field names, and the rail table adds visual noise, but no sentence is truly wasted.

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 an 8-parameter, paid, mutation-free tool with no annotations and no output schema, the description covers purpose, cost, payment mechanism, and result contents. However, it leaves an agent unsure whether the x_* payment parameters must be supplied on a first call and which rail to prefer, which is a material gap for correct invocation.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, so the description must compensate and it only partly does: it adds real constraints for name (min 2 chars), type ('individual'/'entity'), country (two-letter), and limit (1-25, default 10). The four x_* payment parameters are only mapped to rails, not explained semantically (e.g. what a valid x_payment_signature or x_sol_payload looks like, or whether they are required to receive results).

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 first sentence names a specific operation (screening check) on a specific resource (person or company) and even states the trigger ('before you deal with them'), which separates it from lookup-style siblings. It stops short of explicitly contrasting with xrplme_entity_lookup or other sibling tools, so a 4 rather than 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?

'Before you deal with them' gives an implied usage context (pre-transaction due diligence), but there is no explicit when-not guidance, no named alternative, and no guidance on which payment rail (XRPL/Solana/Base) an agent should choose. Usage is inferable but not spelled out.

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.