ripio-community-mcp

Overview Schema Source Related Servers Discussions Admin

Ripio Wallet transaction

ripio_get_transaction

Read-onlyIdempotent

Retrieve complete details of a wallet transaction by its ID, including amounts, fees, rail, counterparty, status, and on-chain hash.

Instructions

Full detail of one Wallet movement by its id (from ripio_list_activity with source "wallet"): amounts, fee, rail, counterparty, status and the on-chain hash when there is one.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Wallet transaction id, as a number or as the string ripio_list_activity returns.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`fee`	No
`date`	Yes
`rail`	No
`type`	Yes
`asset`	Yes
`amount`	Yes
`status`	Yes
`direction`	Yes
`fee_asset`	No
`raw_status`	Yes
`unreadable`	No
`description`	No
`counterparty`	No
`transaction_hash`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.2.3Sep 26, 2026

addedOutput schema / properties / unreadable

Added value: +{
+  "items": {
+    "enum": [
+      "amount",
+      "asset"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

First observedv0.1.1Sep 24, 2026

TDQS

A4.3/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 covered. The description adds a useful conditional ('on-chain hash when there is one') and scopes the resource to wallet movements, but does not discuss not-found behavior or errors. This is adequate but not rich.

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?

One compact sentence, front-loaded with the core purpose and field list; no filler. The parenthetical source guidance is placed right after the id reference, keeping related information together.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a single well-documented parameter, rich annotations, and an output schema present, the description covers what an agent needs to select and invoke the tool. The only omitted details (error behavior) are not necessary given the read-only, idempotent annotations and output schema.

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 coverage is 100% and the schema already describes id as a number or the string ripio_list_activity returns. The description adds the extra constraint that the id must come from entries with source 'wallet', which is meaningful beyond the schema. Baseline 3 is therefore raised slightly.

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?

Description uses a specific verb ('Full detail') and names the exact resource ('one Wallet movement') plus a concrete field list (amounts, fee, rail, counterparty, status, on-chain hash). It also anchors the id source to ripio_list_activity with source 'wallet', distinguishing it from other Ripio tools. This is unambiguous and differentiated.

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?

It explicitly tells the agent where the id comes from ('from ripio_list_activity with source "wallet"'), which is the correct precursor call. It doesn't spell out when not to use it, but for a single-id fetch this is sufficient context. No misleading alternatives are mentioned.

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

Deploy Server