Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

What your watched wallets did (paid)

watched_events

What the wallets on your watchlist did since you last checked each one (or the last hours you ask for), labelled with your names: transfers in and out, tokens, amounts, USD at today's prices, counterparties and links. Five wallets per call; pass offset for the next five. Marks them checked. Needs your agent key.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoLook back this many hours instead of since the last check (max 168)
offsetNoSkip this many wallets (pages of 5)
addressNoOnly this watched wallet

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations flag readOnlyHint=false and openWorldHint=true, and the description explains the underlying side effect: the call 'marks them checked', which is exactly the mutation an agent needs to know about for a non-readonly tool. It also discloses the agent-key auth requirement and the five-wallets-per-call paging cap, adding real value beyond the annotations; it stops short of stating cost or rate limits despite the '(paid)' title.

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 compact sentences, front-loaded with the returned data then the paging mechanics. Slightly awkward phrasing ('the last hours you ask for') and a trailing auth note, but nothing is wasted.

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 3-optional-parameter read tool with no output schema, the description covers what comes back, why the last-check watermark matters, paging behavior, and auth. Missing only cost/cadence information implied by the '(paid)' title, which is a minor gap.

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 coverage is 100%, so all three parameters are already documented, including the 168-hour cap and offset paging. The description reinforces the offset semantics ('pass offset for the next five') and clarifies that hours overrides the last-check watermark, but adds no syntax or format detail beyond the schema — baseline 3.

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?

Names a specific verb and resource — what the wallets on your watchlist did — and enumerates the payload (transfers in/out, tokens, amounts, USD values, counterparties, links). It implicitly separates itself from generic wallet lookups by scoping to the watchlist, though it never names a sibling tool explicitly.

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

Usage Guidelines3/5

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

Usage is implied by 'since you last checked each one (or the last hours you ask for)' and it gives operational paging rules ('Five wallets per call; pass offset for the next five'), plus the 'Needs your agent key' prerequisite. There is no explicit statement of when to prefer this over a general wallet-events tool or when not to use it.

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