AgentTrust

by eamwhite1

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Get XRP Price

get_xrp_price

Read-onlyIdempotent

Get the current live XRP price in USD and GBP.

Instructions

Get the current live XRP price in USD and GBP.

Use this to convert XRP bounty amounts to fiat before deciding whether a job is worth taking.

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": "get_xrp_price"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 7, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds 'live', implying non-cached real-time retrieval, but says nothing about rate limits, cache/freshness windows, or failure modes when the price feed is unavailable.

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?

Two short sentences, zero filler, with the what front-loaded and the when following it. Every sentence earns its place.

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?

With an output schema present, return values needn't be documented, annotations cover the safety profile, and there are no parameters to explain, so the description is nearly complete. The one meaningful omission for a price tool is data freshness/latency beyond the word 'live'.

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 tool takes zero parameters (additionalProperties: false), so there is no parameter semantics for the description to compensate for; baseline for a 0-param tool is 4. The description usefully confirms the output denomination (USD and GBP), which is the only input-adjacent choice an agent might otherwise wonder about.

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?

States a specific verb and resource ('Get the current live XRP price') plus the returned currencies (USD and GBP), so the agent knows exactly what it fetches. It does not explicitly differentiate itself from the sibling quote tools (get_rlusd_quote, get_dex_quote), though the resource name makes the distinction inferable.

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?

Gives a concrete when-to-use: convert XRP bounty amounts to fiat before deciding whether a job is worth taking, which ties the tool to a real workflow step. It offers no exclusions or alternatives (e.g., when to prefer get_rlusd_quote or get_dex_quote), so it stops short of full routing guidance.

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

Deploy Server