NythosX Market Data

get_support_resistance

Support and resistance map. Up to five support and five resistance levels from clustered daily swing pivots, high-volume nodes and round numbers, each with kind, strength (1-5) and touch count, plus the nearest level on each side. Computed from the last 30 daily candles (cached 15 minutes). Use nearestSupport/nearestResistance as stop-loss/take-profit anchors for a position already open; higher strength and touch count mean a more reliable level. Costs $0.005 USDC per call (x402).

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_support_resistance"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	Yes	Instrument symbol

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so well: it discloses the data window (last 30 daily candles), cache duration (15 minutes), pricing ($0.005 USDC via x402), and the meaning of the returned fields (kind, strength 1-5, touch count). This is far more than the schema provides and gives an agent what it needs to judge cost, freshness and interpretation.

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 what the tool returns, then computation, then usage, then cost. Every sentence adds information: level composition, data window/cache, practical anchoring guidance, and pricing. No filler.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must explain the return shape, and it does: up to five support and five resistance levels, each with kind, strength and touch count, plus nearest levels on each side. It also covers freshness, caching and cost, leaving no significant gap for an agent calling this tool.

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?

There is only one parameter, symbol, and the schema fully documents it with an enum of allowed values. The description adds no additional parameter-level meaning beyond the schema, but with a single fully covered parameter the baseline of 4 is appropriate.

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 the exact resource and what it contains: a support/resistance map with up to five levels per side, derived from clustered swing pivots, volume nodes and round numbers. This clearly distinguishes it from siblings such as get_market_regime or get_trade_plan, which do not produce level maps.

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 a concrete usage scenario: use nearestSupport/nearestResistance as stop-loss/take-profit anchors for an already-open position, and explains that higher strength/touch count means more reliability. It lacks explicit when-not-to-use guidance or named alternatives, which keeps it from a 5.

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

All NythosX Market Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?