Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_correlation

Measure whether a coin's returns track BTC using Pearson correlation over 7d or 30d, with a strength label for quick interpretation.

Instructions

Use when the user asks if a coin just tracks BTC. Returns Pearson correlation (-1 to +1) of returns vs BTC over 7d (1h candles) or 30d (4h); no 24h. With strength label. Top 50 Hyperliquid perpetuals by 30-day volume only (see get_supported_assets), others unpaid. Ex: symbol=ETH, period=30d Costs $0.003 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_correlation"
  }
}

Input Schema

NameRequiredDescriptionDefault
periodNo7d
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?

No annotations are supplied, so the description carries the burden and does well: it discloses the output (correlation coefficient plus a strength label), the candle resolution behind each period, the universe restriction to top-50 Hyperliquid perps by 30-day volume, and per-call cost. It omits what happens for an unsupported or unpaid symbol, or error behavior.

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?

Front-loads the trigger, then result, then scope, then example, then price — every clause adds information. The telegraphic style is dense but has no filler sentences.

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, no-annotation, no-output-schema tool, the description covers result semantics, valid inputs, universe limits, and cost. Error paths and default-period behavior (7d default appears only in the schema) are the remaining gaps.

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 description coverage is 0%, so the description must compensate and largely does: it enumerates valid period values (7d/30d, explicitly not 24h), explains the candle interval each implies, and shows a symbol example plus the constraint that symbols must be in the top-50 volume set. Some symbol syntax detail (case, invalid handling) is still missing.

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?

States a specific computation (Pearson correlation of returns vs BTC) on a named resource, with the exact question it answers ("is a coin just tracking BTC"). Clearly distinguishable from siblings like get_coin_strength or get_prices, which do not measure correlation to BTC.

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?

Opens with an explicit trigger ("Use when the user asks if a coin just tracks BTC") and rules out a period option ("no 24h"), and points to get_supported_assets for the covered universe. It does not name a sibling to use instead for related-but-different questions, but the when-to-use guidance is clear.

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