Nota

Move Base Rate

move_base_rate

Read-only

Empirical probability that a token moves k ATRs (up or down, touched or closed beyond) within h days, counted from ~400 days of OKX daily candles on days in the same ATR tercile as today, with a time-split holdout. Pass RYO's atr_14_pct to measure the distance in RYO's ATR; k=0 with event=close gives the plain 'higher after h days' rate.

Input Schema

TableJSON Schema

Name	Required	Description
`k`	No	Distance in ATRs (default 1)
`as_of`	No	YYYY-MM-DD: use only candles closed before this day (scoring a past call)
`event`	No	Default touch
`symbol`	Yes	Token symbol, e.g. SOL
`direction`	No	Default up
`atr_14_pct`	No	RYO's ATR(14) as % of price (analyze_token or deep_analysis)
`horizon_days`	No	1 to 14 (default 3)

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.

Changed1 schema field changedSep 19, 2026

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.4/5.0

Behavior4/5

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

Beyond the readOnlyHint=true annotation, the description discloses the empirical methodology: ~400 days of OKX daily candles, ATR tercile conditioning, and time-split holdout. It also reveals the edge-case behavior of k=0 and event=close. No contradiction with annotations.

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 dense and front-loaded with the key definition, and every sentence adds meaningful information. It loses a point for using 'h days' without explicitly mapping h to horizon_days and for leaving RYO jargon unexplained, which could briefly confuse an agent.

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 7-parameter tool, the description covers the core calculation, data source, conditioning, and special parameter combinations, while the output schema presumably covers return shape. Minor gaps include not explaining the as_of scoring nuance or the exact effect of the time-split holdout on interpretation, but overall it is sufficiently complete.

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?

With 100% schema coverage, the baseline is 3, but the description adds real semantic value: it explains the meaning of k and h, tells how atr_14_pct should be sourced and used, and clarifies the k=0/event=close interaction. This goes well beyond the generic schema descriptions.

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 states the tool's core output: an empirical probability that a token moves k ATRs within h days. It is specific about the data source, conditioning, and validation, and the niche 'base rate' purpose clearly distinguishes it from the listed siblings like crowd_odds or liquidity_check.

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 explicit usage instructions for special cases: passing atr_14_pct to measure in RYO's ATR and using k=0 with event=close to get the plain higher-after-h-days rate. It does not explicitly name alternatives or state when not to use the tool, but the context is clear and actionable.

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.