Skip to main content
Glama
Sign In

Hunter Killer

by io.github.Irishman-Management-LLC
OverviewDiscussionsAdmin

Public wall clusters

get_magnet_levels_teaser
Read-only

Returns the three largest liquidation clusters per side for BTC and ETH from the public delayed wall snapshot.

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

Input Schema

NameRequiredDescriptionDefault
symbolNoOptional: BTCUSDT or ETHUSDT (the free-teaser majors). Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the data is delayed (stale) and capped at three clusters per side, which materially affects how an agent should treat the results. It stops short of stating how delayed the snapshot is or whether results are cached.

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

Conciseness5/5

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

A single sentence that front-loads the core output ('three largest liquidation clusters per side') and then the scope and data source. No redundant or filler wording.

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 one optional parameter and no output schema, the description carries the return-shape burden and does so reasonably: it tells the agent to expect three clusters per side for two symbols. The main remaining gap is the degree of delay in the snapshot, which matters for a time-sensitive liquidation tool.

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 the single optional symbol parameter is already documented in the schema with its allowed values (BTCUSDT/ETHUSDT) and omit-for-both behavior. The description adds no further parameter meaning, so baseline 3 applies.

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 verb and resource ('Returns the three largest liquidation clusters per side') and scopes it to BTC and ETH from a 'public delayed wall snapshot'. An agent can distinguish this teaser from the fuller siblings (e.g. get_liquidation_magnets, hk_levels) by the 'three largest' cap and 'delayed' qualifier, though no sibling is named 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 only implied: the 'teaser'/'public delayed' framing suggests a free preview rather than the authoritative dataset, but the description never says when to prefer it over get_liquidation_magnets or the other liquidation tools. No exclusions or prerequisites are stated.

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

All Hunter Killer 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