Skip to main content
Glama

get_support_resistance_zones

Read-only

Returns support and resistance zones for one coin on Binance perpetuals, for one to three timeframes. Read-only. Per timeframe: up to 3 support and 3 resistance zones, ranked outward from price, each with its low and high, distance from…

Instructions

Returns support and resistance zones for one coin on Binance perpetuals, for one to three timeframes. Read-only. Per timeframe: up to 3 support and 3 resistance zones, ranked outward from price, each with its low and high, distance from price, bars touched in the last 90, tests in the last 30, last touch, and whether it flipped between support and resistance after two closes through it. Also returns volume against its 20-bar average and flags such as no zone above (price above every zone in its history). Use with get_trade_call or get_market_regime for the same coin. (Beta)

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": {
      "coin": "<coin>",
      "timeframes": "<timeframes>"
    },
    "name": "get_support_resistance_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin symbol, e.g. BTC or ETH.
venueNoVenue: BINANCE, the default and the only value.
timeframesYesOne to three candle timeframes, e.g. ["1h", "4h"]. One result per timeframe.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.35.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description still adds substantive behavior beyond that, spelling out per-timeframe zone limits, ranking direction, touch/flip logic, and special flags such as 'no zone above'. It does not cover failure behavior for an unknown coin or any latency/rate considerations.

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?

Purpose and scope are front-loaded in the first sentence, and the dense enumeration of returned fields earns its place because there is no output schema. The middle sentence is long and comma-chained, which slightly hurts scanability, but there is no 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?

With no output schema, the description carries the return-value burden and does so thoroughly, describing zones, distances, touch counts, flip status, and volume context. For a read-only beta tool this is close to sufficient; only error conditions and the redundant 'venue' parameter are left 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 the baseline is 3, and the description adds only modest extra meaning: it clarifies that zones are ranked outward per timeframe and that results are produced per timeframe. The 'venue' parameter is never mentioned, and no format or edge-case guidance is added for coin or timeframe selection.

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 verb and resource ('Returns support and resistance zones'), the exact venue/market ('one coin on Binance perpetuals'), and the scope ('one to three timeframes'). It is clearly distinguishable from sibling tools like get_trade_call or get_market_regime, which it names as complements rather than substitutes.

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

Usage Guidelines3/5

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

It says to 'Use with get_trade_call or get_market_regime for the same coin', which establishes pairing context but not selection criteria: there is no statement of when to choose this tool over a sibling or when it is unnecessary. Usage is implied rather than explicitly bounded.

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