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

@xrpl-utilities/mcp

by XRPL-Utilities
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

xrpl_flows_launch_impact

Quantify XRP ETF launch effects by measuring exchange-flow delta and DEX volume in the 30-day window around each launch date.

Instructions

Free. Per-ETF launch-window analysis: [L-30, L+30] exchange-flow delta and DEX volume around each tracked XRP-exposure ETF launch date.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "xrpl_flows_launch_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.184

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of disclosing behavior. It states that the tool is 'Free' and describes the exact computation (exchange-flow delta and DEX volume) over a defined window. While it does not detail output format or data sources, the read-only analytical nature is clear, and the description adds meaningful context about the launch-window scope.

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 sentence that is compact and front-loaded with 'Free' followed by the core analysis details. Every word contributes to the meaning, and there is no redundancy or 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 tool with no parameters and no output schema, the description covers the essential context: the time window, metrics, and subject. However, it leaves 'tracked XRP-exposure ETF' and the exact definition of 'L' slightly implicit, which could be clarified. Overall, it is sufficiently complete for a zero-param analytical tool.

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?

The input schema is empty with no parameters, so the baseline is 4. The description reinforces that the analysis is fixed around ETF launch dates without requiring user input, making parameter documentation unnecessary.

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 description clearly states the tool's purpose: 'Per-ETF launch-window analysis: [L-30, L+30] exchange-flow delta and DEX volume around each tracked XRP-exposure ETF launch date.' This specifies the exact computation, metrics, and scope, distinguishing it from sibling tools like xrpl_flows_etf_flow_summary and xrpl_flows_exchange_flow_delta.

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?

The description provides clear context for when to use this tool: when one needs to analyze exchange-flow delta and DEX volume around XRP ETF launch dates. It does not explicitly mention alternatives or exclusions, but the specific use case is evident from the description, earning a 4 rather than a 5.

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