Nota

Positioning Check

positioning_check

Read-only

Decide, field by field, whether RYO's deep_analysis derivatives block can be cited as evidence about this token (identical values across other tokens, sign conflicts with OKX coin-terms open interest), and report OKX perp positioning: premium over spot on OKX and Hyperliquid, 24 h open-interest change in coins, long/short account ratio and its 100-hour percentile, and for BTC/ETH Deribit's DVOL implied 7-day move as a check on stop distance.

Input Schema

TableJSON Schema

Name	Required	Description
`symbol`	Yes	Token symbol, e.g. SOL
`atr_stop_pct`	No	Stop distance in % of price (e.g. RYO's 1.5 x atr_14_pct), checked against the DVOL implied 7-day move
`peer_derivatives`	No	Same-day RYO derivatives blocks for other symbols: [{symbol, funding_rate_bps, open_interest_change_24h_pct}]; taken from the day's scorecard locks when omitted
`ryo_btc_funding_bps`	No	Latest BTC funding from RYO monitor_market_sentiment_shift (evidence.funding.latest_bps)
`reference_derivatives`	No	RYO deep_analysis data.derivatives for this symbol; fetched from RYO when omitted and a RYO key is set

Output Schema

TableJSON Schema

Name	Required	Default
`data`	No
`tool`	Yes
`as_of`	No
`status`	Yes
`request`	No
`summary`	No
`trace_id`	No
`warnings`	No
`data_mode`	No	unknown
`availability`	No
`schema_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 19, 2026

addedInput schema / properties / atr_stop_pct

Added value: +{
+  "description": "Stop distance in % of price (e.g. RYO's 1.5 x atr_14_pct), checked against the DVOL implied 7-day move",
+  "type": "number"
+}

changedInput schema / properties / peer_derivatives / description

Previous value: -"Same-day RYO derivatives blocks for other symbols: [{symbol, funding_rate_bps, open_interest_change_24h_pct}]"New value: +"Same-day RYO derivatives blocks for other symbols: [{symbol, funding_rate_bps, open_interest_change_24h_pct}]; taken from the day's scorecard locks when omitted"

changedInput schema / properties / reference_derivatives / description

Previous value: -"RYO deep_analysis data.derivatives for this symbol"New value: +"RYO deep_analysis data.derivatives for this symbol; fetched from RYO when omitted and a RYO key is set"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$defs": {
+    "Summary": {
+      "additionalProperties": true,
+      "properties": {
+        "headline": {
+          "default": "",
+          "title": "Headline",
+          "type": "string"
+        },
+        "key_points": {
+          "items": {
+            "type": "string"
+          },
+          "title": "Key Points",
+          "type": "array"
+        }
+      },
+      "title": "Summary",
+      "type": "object"
+    }
+  },
+  "additionalProperties": true,
+  "properties": {
+    "as_of": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "As Of"
+    },
+    "availability": {
+      "additionalProperties": true,
+      "title": "Availability",
+      "type": "object"
+    },
+    "data": {
+      "additionalProperties": true,
+      "title": "Data",
+      "type": "object"
+    },
+    "data_mode": {
+      "default": "unknown",
+      "enum": [
+        "live",
+        "mixed",
+        "simulated",
+        "unknown"
+      ],
+      "title": "Data Mode",
+      "type": "string"
+    },
+    "request": {
+      "additionalProperties": true,
+      "title": "Request",
+      "type": "object"
+    },
+    "schema_version": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "integer"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Schema Version"
+    },
+    "status": {
+      "enum": [
+        "ok",
+        "partial",
+        "unavailable"
+      ],
+      "title": "Status",
+      "type": "string"
+    },
+    "summary": {
+      "$ref": "#/$defs/Summary"
+    },
+    "tool": {
+      "title": "Tool",
+      "type": "string"
+    },
+    "trace_id": {
+      "anyOf": [
+        {
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "default": null,
+      "title": "Trace Id"
+    },
+    "warnings": {
+      "items": {
+        "type": "string"
+      },
+      "title": "Warnings",
+      "type": "array"
+    }
+  },
+  "required": [
+    "tool",
+    "status"
+  ],
+  "title": "Envelope",
+  "type": "object"
+}

AddedSep 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

The description goes beyond the read-only/destructive annotations by revealing the tool's internal decision behavior: it compares identical values across peers, checks sign conflicts with OKX open interest, and reports multiple positioning metrics rather than just fetching numbers. It does not mention fallback fetching or rate limits, but annotations and the output schema cover much of the safety profile.

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?

The description is a single dense sentence but it is front-loaded with the core decision and has no filler; each clause maps to a real behavior or output metric. It is somewhat run-on, but the information density is appropriate for the tool's complexity.

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 5-parameter tool with nested objects and an output schema, the description covers the central decision logic and the complete list of reported metrics. It leaves optional-parameter handling to the schema and does not add sibling routing guidance, but it is functionally complete for an agent that can read the schema.

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 coverage is 100% with rich parameter descriptions, so the baseline is 3. The description adds value by linking peer_derivatives to the 'identical values' evidence check and clarifying that atr_stop_pct is checked against the DVOL 7-day move, reinforcing the role of parameters already documented in the schema.

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 action ('Decide, field by field...') and names the exact resource (RYO's deep_analysis derivatives block) plus the output scope (OKX/Hyperliquid perp positioning, Deribit DVOL). This is tightly differentiated from siblings like liquidity_check and price_crosscheck, so an agent can tell what the tool does without inspecting the schema.

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?

The description gives a clear context: use this when you need to decide whether the deep_analysis derivatives block is citable evidence and want a full perp positioning report. It does not name alternatives or exclusions, but the purpose is specific enough that routing is unlikely to be ambiguous.

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

All Nota 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.