Skip to main content
Glama
Sign In
@xrpl-utilities/mcp

@xrpl-utilities/mcp

by XRPL-Utilities
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

xrpl_trust_operator_drilldown

Deep dive into a single PermissionedDomain operator: examine domains, credentials, jurisdiction, DID identity, institutional issuers, and lifecycle events for thorough trust assessment.

Instructions

Paid ($0.10 USD). Deep dive on one PermissionedDomain operator: domains, credentials, jurisdiction, DID identity, institutional issuers, and lifecycle events.

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

Input Schema

NameRequiredDescriptionDefault
owner_addressYesXRPL r-address of the operator.
payment_signatureNox402 payment header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.184

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It transparently states the cost ($0.10 USD) and lists the types of information returned. However, it does not mention whether the operation is read-only, how payment is processed, or what the response format looks like, leaving notable gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that immediately highlights the paid nature and cost, then succinctly enumerates the scope. Every word earns its place with no redundancy or irrelevant detail.

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?

Given the absence of an output schema, the description should explain return behavior and any prerequisites more thoroughly. It lists content categories and cost but does not clarify the payment workflow (payment_signature is not required in the schema), error conditions, or why the tool is worth using versus other operator tools. It is adequate but leaves important gaps for an agent to act confidently.

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 coverage is 100% with both parameters already described in the input schema. The description adds the cost context for payment_signature but does not directly explain the parameters beyond what the schema already provides. It does not compensate for or extend parameter semantics significantly.

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 clearly states the tool performs a 'deep dive' on one PermissionedDomain operator, listing specific content areas (domains, credentials, jurisdiction, DID identity, institutional issuers, lifecycle events). This distinguishes it from sibling tools like xrpl_trust_operator_attribution by emphasizing depth, though the verb 'deep dive' is less direct than 'get' or 'list'.

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 implies the tool should be used when an agent needs comprehensive detail on a single operator, but it does not explicitly state when to use it over alternatives or mention any exclusions. Sibling tools such as xrpl_trust_list_operators_index and xrpl_trust_operator_attribution exist, but no comparison is given.

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

Deploy Server

Other Tools