Skip to main content
Glama
Sign In

Fivebar Trading

by io.github.fivebar-xyz
OverviewDiscussionsAdmin

Watch a wallet (paid)

watch_wallet
Idempotent

Add a wallet to your watchlist with a private name ("Treasury", "Dev wallet of XYZ"), or rename one already on it. Labels are private to your agent key. Then watched_events tells you what your wallets did since you last checked. Paid: needs an agent key from https://fivebar.xyz/x402/watch/watch10 ($5, 10 wallets, 30 days) or watch50 ($20, 50 wallets), sent as Authorization: Bearer .

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

Input Schema

NameRequiredDescriptionDefault
labelNoA private name for it, up to 60 characters
chainsNoChains to watch it on, 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: -"Chains to watch it on, default all: robinhood,base,ethereum,arbitrum,hyperevm"New value: +"Chains to watch it on, 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=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: labels are private to the agent key, and access requires a paid bearer key with named tiers and limits. It does not describe the immediate response after adding or what happens with an invalid/expired key, which keeps it short of a 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?

Three sentences, front-loaded with the action and its two modes, then the follow-up tool, then the payment requirement. The pricing URL and tier details are verbose but necessary for a paid tool. Minimal waste overall.

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 and only three simple params, the definition covers action, renaming, label privacy, follow-up tool, and auth/cost. The main omission is what a successful add returns (confirmation, address normalization), which an agent might want for verification.

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, but the description adds meaning the schema lacks: the label is private per agent key and doubles as the identifier used when renaming an entry already on the watchlist. Example label values also clarify the intended granularity. The chains default is already in the schema, so no extra credit there.

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 verb and resource ('Add a wallet to your watchlist') and also covers the rename case ('or rename one already on it'). It distinguishes itself from the sibling watched_events by casting that tool as the downstream read step, so an agent can tell the two apart immediately.

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 gives a clear usage chain: call this to register a wallet, then call watched_events to see activity since the last check. It also states the prerequisites (agent key, pricing tiers) that gate invocation. It does not explicitly contrast with unwatch_wallet or upgrade_watch, but the usage context is unambiguous.

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