Skip to main content
Glama

Full Technical Analysis

coin_analysis
Read-only

Get detailed analysis for a specific asset (coin or stock) on specified exchange and timeframe.

This is the canonical single-symbol technical readout (there is no
"get_technical_analysis" or "get_technical_summary" tool — use THIS one).
Use `multi_timeframe_analysis` instead when you need trend alignment
across several timeframes, and `combined_analysis` when you also want
news sentiment + headlines in the same call. Futures contracts (ES1!,
CL1!, …) and oil/gas/copper are quoted by the futures_* tools, not
analysed here; gold, silver, platinum and palladium are (GC1! → TVC:GOLD).

Example: coin_analysis(symbol="BTCUSDT", exchange="BINANCE", timeframe="1h")

Args:
    symbol: Bare ticker, no exchange prefix — crypto: "BTCUSDT", "ETHUSDT"; stocks: "COMI" (EGX), "THYAO" (BIST), "600519" (SSE), "300251" (SZSE), "2330" (TWSE), "3105" (TPEX)
    exchange: Exchange — crypto: KUCOIN, BINANCE, MEXC; stocks: EGX, BIST, NASDAQ, NYSE, BURSA, HKEX, SSE, SZSE, TWSE, TPEX, EPA (Euronext Paris), AMS, BRU, LIS, MIL, LSE, SIX, BME, XETRA, FWB, TSX, TSXV, NSE, BSE (India), IDX (Indonesia). If the symbol isn't listed there, the error's `listed_on` field names exchanges that do list it.
    timeframe: Time interval (5m, 15m, 1h, 4h, 1D, 1W, 1M)

Returns:
    Detailed analysis with all indicators and metrics

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "coin_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes
exchangeNoKUCOIN
timeframeNo15m

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover the read-only, non-destructive, open-world profile, so the description need not restate safety. It adds real behavioral context beyond them: symbol coverage by exchange and market, an error contract (the `listed_on` field names exchanges that do list an unlisted symbol), and the futures/metals scope boundary. The remaining gap is return detail — 'all indicators and metrics' does not say which indicators or how they are shaped.

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?

Front-loaded with purpose, then routing, then a worked example, then Args/Returns — a clean structure that is easy to scan. The parenthetical about tools that do not exist is slightly defensive and the exchange list is long, but both earn their space for an agent that cannot inspect the enum-less schema.

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?

Given three parameters, no output schema, and no sibling-level detail available elsewhere, the description covers inputs thoroughly and correctly bounds scope. The one shortfall is the Returns section, which is a single vague line ('Detailed analysis with all indicators and metrics') and, with no output schema present, leaves the agent guessing at the payload's contents.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% — all three parameters are bare typed properties with defaults — so the description carries the full burden and does so: symbol format (bare ticker, no exchange prefix) with per-market examples (BTCUSDT, COMI, THYAO, 600519, 2330), an extensive exchange enumeration with regional glosses (EPA = Euronext Paris, BSE = India), and the accepted timeframe values (5m…1M). Without this, the defaults (KUCOIN, 15m) would be the only guidance an agent had.

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 opens with a specific verb and resource ('Get detailed analysis for a specific asset ... on specified exchange and timeframe') and explicitly asserts it is the canonical single-symbol readout, even pre-empting non-existent lookalike tool names. An agent can distinguish it from multi_timeframe_analysis and combined_analysis 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?

Explicit routing rules are given: use multi_timeframe_analysis for trend alignment across timeframes, combined_analysis when news sentiment and headlines are also needed, and futures_* tools for futures contracts and oil/gas/copper. Exclusions (futures not analysed here, precious metals are) are stated, which is exactly the when-not guidance most definitions lack.

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.