Skip to main content
Glama
Sign In

CryptoKeyhole

by com.cryptokeyhole
OverviewDiscussionsAdmin

Metrics at extremes

find_extremes
Read-onlyIdempotent

Which charts of a coin, or of every coin, stand furthest from normal right now: each chart's latest reading against its own last four years (z-score and percentile), high or low, with the days since it was last this far out. The quickest way to see what is unusual on chain, in derivatives or in flows today. Without an API key it shows the top rows of the free charts and counts the rest by the plan that shows them.

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

Input Schema

NameRequiredDescriptionDefault
assetNoCoin code, for example BTC or ETH, or ALL for every coin.BTC
limitNoRows to return.
queryNoOptional words a chart's name, id or folder must hold, for example "exchange", "funding" or "miners".
intervalNoResolution: 24h daily. get_metric_metadata gives the intervals a metric offers.24h
directionNoCharts unusually high, unusually low, or both.both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / asset / enum
      Previous value: -[
-  "BTC",
-  "ETH",
-  "SOL",
-  "XRP",
-  "TRX",
-  "BNB",
-  "DOGE",
-  "TON",
-  "LINK",
-  "HYPE",
-  "WBTC",
-  "ADA",
-  "NEAR",
-  "XLM",
-  "BCH",
-  "XMR",
-  "LTC",
-  "UNI",
-  "AVAX",
-  "SUI",
-  "HBAR",
-  "WLD",
-  "WLFI",
-  "LIT",
-  "MNT",
-  "SHIB",
-  "QNT",
-  "ENA",
-  "TAO",
-  "MORPHO",
-  "AAVE",
-  "ONDO",
-  "DOT",
-  "ZRO",
-  "PEPE",
-  "SKY",
-  "ICP",
-  "ARB",
-  "PUMP",
-  "ETC",
-  "KAS",
-  "ASTER",
-  "FF",
-  "POL",
-  "APT",
-  "INJ",
-  "ALGO",
-  "RENDER",
-  "JUP",
-  "CAKE",
-  "ATOM",
-  "CRV",
-  "ZAMA",
-  "XTZ",
-  "SENT",
-  "ETHFI",
-  "FIL",
-  "STX",
-  "AERO",
-  "VET",
-  "PENDLE",
-  "ENS",
-  "DASH",
-  "PENGU",
-  "FET",
-  "TRUMP",
-  "PYTH",
-  "VIRTUAL",
-  "NEO",
-  "THETA",
-  "TIA",
-  "LDO",
-  "KAIA",
-  "MANA",
-  "CHZ",
-  "FARTCOIN",
-  "EIGEN",
-  "SPX",
-  "EDGE",
-  "SEI",
-  "RUNE",
-  "ZK",
-  "RAY",
-  "IMX",
-  "AXS",
-  "OP",
-  "DYDX",
-  "SNX",
-  "JASMY",
-  "RSR",
-  "BAT",
-  "GRT",
-  "SYRUP",
-  "STRK",
-  "WIF",
-  "GMX",
-  "LPT",
-  "YFI",
-  "JTO",
-  "FLOKI",
-  "COMP",
-  "SAND",
-  "APE",
-  "PROM",
-  "ALT",
-  "GALA",
-  "NIL",
-  "ERA",
-  "ALL"
-]New value: +[
+  "BTC",
+  "ETH",
+  "SOL",
+  "XRP",
+  "TRX",
+  "BNB",
+  "DOGE",
+  "TON",
+  "LINK",
+  "ZEC",
+  "HYPE",
+  "WBTC",
+  "ADA",
+  "NEAR",
+  "XLM",
+  "BCH",
+  "XMR",
+  "LTC",
+  "UNI",
+  "AVAX",
+  "SUI",
+  "HBAR",
+  "WLD",
+  "WLFI",
+  "LIT",
+  "MNT",
+  "SHIB",
+  "QNT",
+  "ENA",
+  "TAO",
+  "MORPHO",
+  "AAVE",
+  "ONDO",
+  "OKB",
+  "CRO",
+  "DOT",
+  "ZRO",
+  "PEPE",
+  "SKY",
+  "ICP",
+  "ARB",
+  "PUMP",
+  "ETC",
+  "KAS",
+  "ASTER",
+  "FF",
+  "POL",
+  "APT",
+  "INJ",
+  "ALGO",
+  "RENDER",
+  "JUP",
+  "CAKE",
+  "ATOM",
+  "CRV",
+  "ZAMA",
+  "XTZ",
+  "SENT",
+  "ETHFI",
+  "FIL",
+  "STX",
+  "AERO",
+  "VET",
+  "PENDLE",
+  "ENS",
+  "DASH",
+  "PENGU",
+  "FET",
+  "TRUMP",
+  "PYTH",
+  "VIRTUAL",
+  "NEO",
+  "THETA",
+  "TIA",
+  "LDO",
+  "KAIA",
+  "MANA",
+  "CHZ",
+  "FARTCOIN",
+  "EIGEN",
+  "SPX",
+  "EDGE",
+  "SEI",
+  "RUNE",
+  "ZK",
+  "RAY",
+  "BONK",
+  "IMX",
+  "AXS",
+  "OP",
+  "DYDX",
+  "SNX",
+  "JASMY",
+  "RSR",
+  "AR",
+  "BAT",
+  "GRT",
+  "SYRUP",
+  "STRK",
+  "WIF",
+  "GMX",
+  "LPT",
+  "YFI",
+  "JTO",
+  "IOTA",
+  "GRASS",
+  "FLOKI",
+  "COMP",
+  "SAND",
+  "APE",
+  "ARKM",
+  "PROM",
+  "EGLD",
+  "ORDI",
+  "KSM",
+  "ALT",
+  "GALA",
+  "NIL",
+  "ERA",
+  "AXL",
+  "ROSE",
+  "ONT",
+  "BRETT",
+  "ZIL",
+  "FLOW",
+  "POPCAT",
+  "PNUT",
+  "MEW",
+  "ENJ",
+  "ALL"
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / asset / enum
      Previous value: -[
-  "BTC",
-  "ETH",
-  "SOL",
-  "XRP",
-  "TRX",
-  "BNB",
-  "DOGE",
-  "TON",
-  "LINK",
-  "HYPE",
-  "WBTC",
-  "ADA",
-  "NEAR",
-  "XLM",
-  "BCH",
-  "LTC",
-  "UNI",
-  "AVAX",
-  "SUI",
-  "HBAR",
-  "WLD",
-  "WLFI",
-  "LIT",
-  "MNT",
-  "SHIB",
-  "QNT",
-  "ENA",
-  "MORPHO",
-  "AAVE",
-  "ONDO",
-  "DOT",
-  "ZRO",
-  "PEPE",
-  "SKY",
-  "ARB",
-  "FF",
-  "POL",
-  "APT",
-  "CRV",
-  "ZAMA",
-  "SENT",
-  "ETHFI",
-  "PENDLE",
-  "ENS",
-  "FET",
-  "LDO",
-  "EIGEN",
-  "SPX",
-  "EDGE",
-  "IMX",
-  "AXS",
-  "BAT",
-  "GRT",
-  "SYRUP",
-  "FLOKI",
-  "COMP",
-  "SAND",
-  "APE",
-  "PROM",
-  "ALT",
-  "GALA",
-  "NIL",
-  "ERA",
-  "ALL"
-]New value: +[
+  "BTC",
+  "ETH",
+  "SOL",
+  "XRP",
+  "TRX",
+  "BNB",
+  "DOGE",
+  "TON",
+  "LINK",
+  "HYPE",
+  "WBTC",
+  "ADA",
+  "NEAR",
+  "XLM",
+  "BCH",
+  "XMR",
+  "LTC",
+  "UNI",
+  "AVAX",
+  "SUI",
+  "HBAR",
+  "WLD",
+  "WLFI",
+  "LIT",
+  "MNT",
+  "SHIB",
+  "QNT",
+  "ENA",
+  "TAO",
+  "MORPHO",
+  "AAVE",
+  "ONDO",
+  "DOT",
+  "ZRO",
+  "PEPE",
+  "SKY",
+  "ICP",
+  "ARB",
+  "PUMP",
+  "ETC",
+  "KAS",
+  "ASTER",
+  "FF",
+  "POL",
+  "APT",
+  "INJ",
+  "ALGO",
+  "RENDER",
+  "JUP",
+  "CAKE",
+  "ATOM",
+  "CRV",
+  "ZAMA",
+  "XTZ",
+  "SENT",
+  "ETHFI",
+  "FIL",
+  "STX",
+  "AERO",
+  "VET",
+  "PENDLE",
+  "ENS",
+  "DASH",
+  "PENGU",
+  "FET",
+  "TRUMP",
+  "PYTH",
+  "VIRTUAL",
+  "NEO",
+  "THETA",
+  "TIA",
+  "LDO",
+  "KAIA",
+  "MANA",
+  "CHZ",
+  "FARTCOIN",
+  "EIGEN",
+  "SPX",
+  "EDGE",
+  "SEI",
+  "RUNE",
+  "ZK",
+  "RAY",
+  "IMX",
+  "AXS",
+  "OP",
+  "DYDX",
+  "SNX",
+  "JASMY",
+  "RSR",
+  "BAT",
+  "GRT",
+  "SYRUP",
+  "STRK",
+  "WIF",
+  "GMX",
+  "LPT",
+  "YFI",
+  "JTO",
+  "FLOKI",
+  "COMP",
+  "SAND",
+  "APE",
+  "PROM",
+  "ALT",
+  "GALA",
+  "NIL",
+  "ERA",
+  "ALL"
+]
  3. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world safety, so the description focuses on output semantics: each row carries a z-score, percentile, high/low direction, and days since the last comparable extreme. It also discloses a meaningful behavioral trait beyond annotations — the unauthenticated/limited-plan behavior of showing top rows of free charts and counting the rest by plan. It stops short of describing pagination or row ordering.

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 core question the tool answers, then the use case, then the access caveat. No filler, though the first sentence is dense enough that the qualifiers ('z-score and percentile', 'days since it was last this far out') take a second read.

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 five-param, optional-argument read tool with full schema coverage and no output schema, the description supplies the essential result shape (z-score, percentile, direction, recency) plus the access limitation. What's missing is minor: ordering of rows, and whether the free-tier behavior affects the reported counts' reliability.

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% and all five parameters have descriptions and enums, so the schema carries the semantics. The description reinforces the asset scoping ('of a coin, or of every coin') and the high/low concept behind the direction parameter, but adds no syntax or constraint detail beyond the schema. Baseline 3 is appropriate.

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 uses a specific verb-and-resource framing ('Which charts of a coin, or of every coin, stand furthest from normal right now') and spells out the metric computed (z-score and percentile of each chart's latest reading against its own four-year history). It is clearly distinguishable from siblings like correlate_metrics, run_formula, or get_metric_metadata, which do different things.

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 states the use case plainly ('The quickest way to see what is unusual on chain, in derivatives or in flows today') and notes the no-API-key fallback behavior. It does not explicitly name an alternative tool or state when-not-to-use it in favor of get_asset_metrics or screen_assets, so it falls short of a 5.

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

All CryptoKeyhole 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