Skip to main content
Glama
Sign In

wallet-tracker

by xyz.cabalspy
OverviewDiscussionsAdmin

get_signal_history

Read-only
Past signals, for checking whether a kind of signal has worked historically
before acting on a live one.

blockchain: solana, bnb, base, eth or rh
wallet_type: kol, smart or whale (default kol)
days: 7, 30, 90 or "all" (default 30)
mode: cluster, entry or exit. Omit for all modes.
limit: how many signals (default 25)

Input Schema

NameRequiredDescriptionDefault
daysNoHow far back to look: 7, 30, 90 or all.30
modeNoRestrict to cluster, entry or exit. Leave empty for every mode.
limitNoHow many entries to return. Keep it small: large results are trimmed to fit the context window anyway.
blockchainYesBlockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2.
wallet_typeNoWallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only.kol

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / blockchain / description
      Previous value: -"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base and rh have kol and smart; eth has kol only. rh is Robinhood Chain, an Ethereum L2."New value: +"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base, eth and rh have kol and smart. rh is Robinhood Chain, an Ethereum L2."
  2. Changed8 schema fields changed
    • addedInput schema / properties / blockchain / description
      Added value: +"Blockchain. One of: solana, bnb, base, eth, rh. solana has kol, smart and whale wallets; bnb, base and rh have kol and smart; eth has kol only. rh is Robinhood Chain, an Ethereum L2."
    • addedInput schema / properties / days / description
      Added value: +"How far back to look: 7, 30, 90 or all."
    • addedInput schema / properties / limit / description
      Added value: +"How many entries to return. Keep it small: large results are trimmed to fit the context window anyway."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / mode / description
      Added value: +"Restrict to cluster, entry or exit. Leave empty for every mode."
    • addedInput schema / properties / wallet_type / description
      Added value: +"Wallet type. kol is a Key Opinion Leader, an influencer whose calls move markets. smart is a wallet selected for its track record. whale is a large holder, Solana only."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "get_signal_historyDictOutput",
+  "type": "object"
+}
  3. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the notion that results are historical snapshots used for validation, but says nothing about auth needs, recency of data, or rate limits beyond what annotations and schema provide.

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

Conciseness3/5

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

The opening sentence is well front-loaded and earns its place, but the subsequent parameter legend repeats content already fully present in the schema, so part of the text does not add value.

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 an output schema present, return values need not be explained, and the description plus annotations cover purpose, valid inputs, and safe-read behavior. It is complete enough for an agent to select and call the tool correctly.

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 every parameter is already documented in the schema. The description's parameter legend largely duplicates the schema's value lists and adds no syntax or format meaning beyond it, making the baseline 3 correct.

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?

The description names a specific resource — past signals — and frames the scope as historical lookup versus 'acting on a live one', which implicitly separates it from get_signals. It does not explicitly name the sibling tool, so it stops just short of a 5.

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 use case: check whether a signal kind has worked historically before acting on a live one. There is no explicit when-not or named alternative, but the triggering context is genuinely useful and unambiguous.

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

All wallet-tracker 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