Nota

Verdict Track Record

verdict_track_record

Read-only

How RYO's own deep_analysis plans have fared: locked daily for 25 majors and settled on OKX hourly candles (stop or +1R target first, 24 h or 72 h). Returns counts by verdict and by confluence state, plans whose verdict leans against their own direction, and the latest locked verdict. Omit the symbol for all tokens.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`symbol`	No	Token symbol, e.g. SOL; omit for every token
`horizon_hours`	No	24 (default) or 72

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.

Changed2 schema fields changedSep 19, 2026

addedInput schema / properties / horizon_hours / enum
```
Added value: +[
+  24,
+  72
+]
```

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

A3.7/5.0

Behavior4/5

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

Annotations already establish read-only and non-destructive behavior, and the description adds meaningful context beyond them: plans are 'locked daily for 25 majors and settled on OKX hourly candles (stop or +1R target first, 24 h or 72 h)'. It also discloses what is returned without contradicting the 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 compact and front-loads the core purpose, followed by methodology and output summary. It has no filler, though the dense parenthetical about settlement rules could be slightly clearer.

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 an output schema present, the description adequately covers purpose, methodology, key output categories, and parameter behavior. It is complete enough for an agent to call correctly, though the meanings of 'verdict' and 'confluence state' are left to surrounding context.

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 both parameters are already documented. The description reinforces 'omit the symbol for all tokens' and the 24/72 hour horizon, but adds no semantic detail beyond the schema.

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 clearly specifies the resource ('RYO's own deep_analysis plans') and what the tool does ('Returns counts by verdict and by confluence state...'). It distinguishes itself from the market-snapshot siblings by focusing on historical verdict performance, but it does not explicitly name or contrast a sibling.

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?

The context implies it should be used when one wants RYO plan-performance breakdowns, and the parameter hints ('Omit the symbol for all tokens', '24 h or 72 h') give operational guidance. However, nothing explicitly states when to choose this over sibling tools or excludes any alternative.

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.