Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_coin_strength

Compare a coin's return to BTC over 24h, 7d, or 30d to see if it is outperforming or lagging, with a strength rating and ratio.

Instructions

Use when the user asks if a coin is outperforming or lagging BTC. Returns its return minus BTC's over 24h, 7d or 30d, a rating (very_strong to very_weak) and the ratio. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=SOL, period=7d Costs $0.015 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_coin_strength"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo24h
symbolNoETH

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key behavior: output format (relative return, rating, ratio), data scope (top 50 Hyperliquid perpetuals by 30-day volume), a cost of $0.015 USDC per call, and an example invocation. It leaves 'others unpaid' ambiguous and does not mention authentication 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 description is front-loaded with the use case, followed by return details, scope, example, and cost. Every sentence adds useful information without repetition or filler.

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 simple two-parameter tool with no output schema, the description covers purpose, return values, scope, cost, and an example. It is nearly complete, though the phrase 'others unpaid' is vague and there is no note on error behavior or authentication.

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. It lists valid period values (24h, 7d, 30d) and gives an example (symbol=SOL, period=7d), clarifying both parameters. It does not explain the default values or what happens when a symbol is outside the top 50, leaving some gaps.

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 specific use case ('if a coin is outperforming or lagging BTC') and precisely what the tool returns: relative return, a rating from very_strong to very_weak, and the ratio. It distinguishes itself from generic price tools by framing the comparison against BTC over selectable periods.

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 an explicit trigger ('Use when the user asks if a coin is outperforming or lagging BTC') and a scope constraint (top 50 Hyperliquid perpetuals by 30-day volume only, see get_supported_assets). However, it does not name an alternative tool for cases outside that scope or explicitly say when not to use it.

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