Skip to main content
Glama

AINDEX

Support, resistance and reference levels

get_levels
Read-only

Previous day, week and month high, low and midpoint with this period's opens, floor pivots from the previous day, support and resistance from clustered swing points (with touches and distance from price), and the volume profile's point of control and value area.

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": "get_levels"
  }
}

Input Schema

NameRequiredDescriptionDefault
venueNo
symbolYes
timeframeNo1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds meaningful content beyond that — it discloses that levels are computed (clustered swing points with touch counts and distance from price, volume profile value area) rather than raw exchange data. It does not disclose data freshness, whether unsupported venues/symbols fail or return empty, or any 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense sentence with every clause earning its place as returned-field inventory, and the most important outputs come first. Readability suffers slightly from the unbroken noun list, but there is no filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 correctly carries the burden of explaining the payload, and it does so thoroughly. However, for a three-parameter tool with two enums and 0% schema coverage, it leaves the input side entirely undocumented, so an agent knows what it gets but not how to configure the call.

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 description coverage is 0%, so the description is the only source of parameter meaning — but it never names symbol, venue, or timeframe. It implicitly conveys that "this period's opens" scale with the timeframe setting, which is the one semantic hint it provides. The venue enum (including the near-duplicate lighter vs lighter-rh) and the 1h default remain unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description enumerates the concrete artifacts returned: prior-period high/low/midpoint, period opens, floor pivots, clustered swing support/resistance, and volume-profile POC/value area. That is specific enough to separate it from get_candles or get_patterns, though it never states a verb ("Returns...") and reads as a noun list rather than a purpose statement.

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

Usage Guidelines2/5

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

There is no guidance on when to call this instead of get_candles, get_patterns, or get_derivatives, and no stated prerequisites (e.g. symbol must be listed on the chosen venue). Usage is only implied by the technical-analysis nature of the returned fields.

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.

Resources