Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

What a wallet did (transfer by transfer)

wallet_events
Read-only

Every token transfer in or out of a wallet over the last hours, newest first, across Robinhood Chain, Base, Ethereum, Arbitrum, HyperEVM and Elysium: time, chain, in or out, token, amount, USD at today's prices, the counterparty, and a link to the transaction. Free, for a one-off look at any wallet. To keep a list of wallets with private names and get what changed since you last checked, use the paid watch_wallet and watched_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": {
      "address": "<address>"
    },
    "name": "wallet_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow far back, default 24, max 168 (a week)
limitNoTransfers to list, default 40, max 100
chainsNoComma-separated chains, default all: robinhood,base,ethereum,arbitrum,hyperevm,elysium
addressYesWallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chains / description
      Previous value: -"Comma-separated chains, default all: robinhood,base,ethereum,arbitrum,hyperevm"New value: +"Comma-separated chains, default all: robinhood,base,ethereum,arbitrum,hyperevm,elysium"
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds genuinely new behavior: it is free, results are ordered newest-first, coverage spans six specific chains, and USD values are priced 'at today's prices'. It stops short of stating pagination behavior or what an empty/invalid-address result looks like, which keeps it at 4 rather than 5.

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

Conciseness4/5

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

Two sentences, front-loaded with what you get, then the cost/alternative routing. The long comma-separated field list is dense but each item is informative; a slight trim would improve scannability without losing meaning.

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 no output schema, the description usefully enumerates the return fields and their ordering, and it resolves the free-vs-paid decision against siblings. Missing only edge-case behavior (empty results, address validation, how limit interacts with ordering) for a read tool that is otherwise well specified.

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 description coverage is 100%, so defaults and maximums for hours, limit, and chains are already documented in structured form. The description only echoes the time window and chain set without adding format or interaction detail (e.g. whether chains filter affects ordering or pricing), so the baseline 3 applies.

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?

States a concrete verb and resource ('every token transfer in or out of a wallet'), plus scope details: recency window, ordering ('newest first'), six named chains, and the exact fields returned. It is immediately distinguishable from watch_wallet/watched_events, which the description explicitly names as the stateful alternative.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames the tool as 'free, for a one-off look at any wallet' and names the alternative path ('to keep a list of wallets with private names and get what changed since you last checked, use the paid watch_wallet and watched_events'). Both the when and the when-not, plus the cost tradeoff, are spelled out.

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

All Fivebar Trading toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources