Nota

Narrative Convergence

narrative_convergence

Read-only

Monitor up to 20 user-selected voices (Telegram public channels, Bluesky and X handles) and report which tokens they mention, lexicon-scored sentiment per token, conviction and urgency, and whether the voices converge: at least two voices carry a non-zero net sentiment on the token and every one of them has the same sign.

Input Schema

TableJSON Schema

Name	Required	Description
`hours`	No	Look-back window in hours (default 24)
`tokens`	No	Symbols to track; default = every cashtag, ticker or name of a known major found
`voices`	Yes	Up to 20 ids like tg:WatcherGuru, bs:handle.bsky.social or x:handle

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

changedInput schema / properties / tokens / description

Previous value: -"Symbols to track; default = every cashtag found"New value: +"Symbols to track; default = every cashtag, ticker or name of a known major found"

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

First observedSep 10, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds substantial behavioral context beyond those: lexicon-scored sentiment, conviction and urgency reporting, a 20-voice limit, and the exact convergence rule of at least two voices with non-zero same-sign net sentiment. 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 a single dense sentence with no filler; it front-loads the monitoring target and includes only essential scope, sources, scoring, and convergence details. It could be lightly restructured for readability, but every clause earns its place.

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 and full parameter descriptions, the description covers the tool's purpose, voice sources and limits, reporting dimensions, and convergence definition. Nothing critical for selecting or invoking the tool is missing, though it does not mention rate limits or latency.

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 100%, so the parameters are already documented in the schema. The description reinforces voices/tokens semantics and ties them to the convergence workflow, but it does not add new parameter-level details beyond what the schema already provides.

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 a specific action ('monitor/report') on a clearly defined resource: up to 20 user-selected voices and the tokens they mention. It also defines the core output precisely with the convergence condition, making it unmistakably distinct from siblings like news_verify or positioning_check.

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 use case is implied clearly: when an agent needs token-level sentiment, conviction, urgency, and convergence across Telegram/Bluesky/X voices, this is the tool. However, it names no alternatives and provides no explicit when-to-use or when-not-to-use guidance relative to the sibling tools.

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.