Skip to main content
Glama
ruizemanuel

ripio-community-mcp

by ruizemanuel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Ripio activity

ripio_list_activity
Read-onlyIdempotent

List wallet and trade activity from Ripio—deposits, withdrawals, swaps, and trades—newest first. Filter by date, currency, type, or rail to isolate specific entries.

Instructions

Deposits, withdrawals and swaps (source "wallet", default) or Ripio Trade statement entries (source "trade"), newest first, in one normalized shape. Card transactions, in-app buys/sells and bill payments are not available from Ripio's API. Pass next_cursor back as cursor for older items. Dates are UTC; on Wallet, from/to filter the returned page only; on Ripio Trade a from/to range can span up to 182 days.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoUTC date (YYYY-MM-DD) or ISO 8601 date-time.
fromNoUTC date (YYYY-MM-DD) or ISO 8601 date-time.
railNoWallet only.
typeNo"trade" exists only in source "trade"; "swap" only in "wallet".
cursorNonext_cursor from a previous call.
sourceNoDefault "wallet".
currencyNoOnly this asset, e.g. "USDT".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
sourceYes
next_cursorNo
coverage_notesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.3
    • addedOutput schema / properties / items / items / properties / unreadable
      Added value: +{
+  "items": {
+    "enum": [
+      "amount",
+      "asset"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}
  2. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already signal readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior; the description adds meaningful operational detail: pagination mechanics, UTC date handling, source-specific from/to semantics, the 182-day trade range limit, ordering, and unsupported transaction types. This goes well beyond the annotations.

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?

Three dense sentences with no filler. The first sentence conveys the core purpose and default, the second lists unavailable categories, and the third packs pagination and date semantics. Every sentence earns its place.

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?

For a tool with 7 optional parameters, two distinct sources, pagination, and source-specific filtering behavior, the description covers all key operational caveats. The output schema exists, so the description does not need to document return values, and no essential preconditions or limitations are missing.

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%, so the baseline is 3. The description adds value by explaining the default source, cursor reuse, source-specific from/to behavior, and type/source associations (trade only in trade, swap only in wallet). Rail and currency remain schema-only, but their descriptions are already clear.

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 states a specific scope: deposits, withdrawals and swaps for the default wallet source, or Ripio Trade statement entries for the trade source, returned newest first in one normalized shape. This clearly distinguishes it from sibling tools like ripio_get_transaction, which retrieves a single transaction.

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 clearly establishes when to use this tool, including the default source, the alternate trade source, and pagination via next_cursor. It does not explicitly name alternative sibling tools for cases like retrieving a single transaction, so it stops short of a 5, but the context is unambiguous.

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