Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_market_silence

Assess whether a Hyperliquid perpetual is unusually quiet with a 0–1 silence score, level, and advice based on volume vs. average, volatility, and 24h change for 7d, 14d, or 30d.

Instructions

Use when the user asks whether a coin is unusually quiet. Returns a 0-1 silence score, level and advice from today's volume vs the period average, volatility and 24h change on Hyperliquid perpetuals (7d, 14d, 30d). For a squeeze use get_compression_alert. Ex: symbol=ETH, period=14d Costs $0.002 USDC per call.

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_market_silence"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo7d
symbolNoBTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the data source (Hyperliquid perpetuals), the outputs produced (score, level, advice), the basis of computation, and an explicit per-call cost of $0.002 USDC. Gaps are minor for a read-only metric tool — no mention of error behavior for unsupported symbols or rate limits.

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?

The trigger is front-loaded, followed by return semantics, the sibling exclusion, a concrete example, and cost — in three tight sentences with no filler. Every clause adds routing or invocation 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?

For a two-parameter, annotation-free tool with no output schema, the description covers trigger, outputs, data source, period range, and pricing. It stops short of describing what the 'level' field's possible values or thresholds are, which would help an agent interpret rather than just call the tool.

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 0%, so the description must compensate, and it partially does: it enumerates the supported periods (7d, 14d, 30d) and gives a concrete example 'symbol=ETH, period=14d', which clarifies that symbol means a Hyperliquid perp ticker. It does not state how invalid symbols or unsupported period strings are handled, leaving some ambiguity.

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 names a specific computation ('silence score' 0-1) and grounds it in concrete inputs: today's volume vs period average, volatility and 24h change on Hyperliquid perpetuals. It also explicitly separates itself from the sibling get_compression_alert, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

It opens with an explicit trigger ('Use when the user asks whether a coin is unusually quiet') and names the alternative with its distinguishing condition ('For a squeeze use get_compression_alert'). That is exactly the when-to-use / when-to-use-something-else guidance the dimension asks for.

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