Skip to main content
Glama

SwapHunt crypto market context

get_market_silence

Read-onlyIdempotent

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 (local package). Ex: symbol=ETH&period=14d Free trial: 10 calls a day. More tools (30, paid per call in USDC via x402): run the local server, uvx swaphunt-mcp, https://x402.swaphunt.dev/docs

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
periodNoLookback: 7d, 14d or 30d7d
symbolNoCoin symbol, e.g. BTC, ETH, SOL (BTCUSDT and BTC-PERP also mean BTC)BTC

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, but the description adds material context not in them: the data source (Hyperliquid perpetuals), the metric construction (today's volume vs. period average), and a hard rate limit of 10 free calls per day with paid access in USDC via x402. What it does not disclose is behavior on edge cases such as a symbol with no Hyperliquid market or insufficient history.

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?

The core is front-loaded: trigger first, return shape second, alternative third, all in short clauses. The trailing promotional material (free trial, 30 other tools, local server command, docs URL) is useful onboarding but sits past the point of decision and could be trimmed.

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, the description carries the return-value burden and does so by naming the score, level and advice fields plus inputs used. Data source, rate limits and pricing are present, so an agent can decide and call correctly; only edge-case/error behavior for unsupported symbols is unaddressed.

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 coverage is 100%, so both parameters and the period enum are already fully documented in the schema. The description only mildly reinforces this by repeating the three lookbacks (7d, 14d, 30d) and showing an example query; it adds no new meaning such as how the period affects the score's sensitivity.

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 concrete question the tool answers ("whether a coin is unusually quiet") and specifies exactly what is returned: a 0-1 silence score, level and advice derived from today's volume vs. the period average, volatility and 24h change on Hyperliquid perpetuals. It routes the nearby concept (squeeze) to get_compression_alert, so an agent can separate it from related tools without opening any 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 gives an explicit trigger ("Use when the user asks whether a coin is unusually quiet") and an explicit alternative for the adjacent case ("For a squeeze use get_compression_alert"). The example invocation `symbol=ETH&period=14d` further grounds correct usage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.