JYOTINT Sealed Forecasts

neural_search

Read-onlyIdempotent

SEMANTIC + ASSOCIATIVE search over the public sealed record and the published site corpus — the JYOTINT public brain (a neural associative memory: frozen deep encoder → Hopfield pattern completion → spreading activation over typed synapses → k-winners-take-all). Finds calls by MEANING, not keywords ('upper-stage anomalies' finds the calls that describe one without those words) and returns the RELATED subgraph, not just isolated hits. Retrieval-only and non-generative: every result is VERBATIM sealed/published text with public provenance (source URL, SHA-256 seal hash, frozen grade) plus an explainable why/activation path and Hopfield convergence info. Prefer this over search_sealed_forecasts for fuzzy/conceptual queries; the REST twin is GET /brain?q=…

Input Schema

TableJSON Schema

Name	Required	Description
`k`	No	Max results, 1–12 (default 6).
`query`	Yes	Natural-language query (e.g. 'what did the record say before the Crocus attack', 'upper stage anomaly calls').
`sensitivity`	No	Recall/precision posture (default balanced). high_recall: miss nothing, accept noise — a planner inside a live window. high_precision: only hits that clear the similarity floor, the rest reported under `withheld` — an office quoting the record outward.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / sensitivity

Added value: +{
+  "description": "Recall/precision posture (default balanced). high_recall: miss nothing, accept noise — a planner inside a live window. high_precision: only hits that clear the similarity floor, the rest reported under `withheld` — an office quoting the record outward.",
+  "enum": [
+    "high_recall",
+    "balanced",
+    "high_precision"
+  ],
+  "type": "string"
+}

AddedAug 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive safety, but the description adds substantial behavioral detail: retrieval-only and non-generative, verbatim text with public provenance, explainable activation paths, and convergence info. It does not contradict 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 purpose and routing guidance are front-loaded and the description is well-structured despite being dense. The parenthetical neural mechanism is somewhat elaborate, but it supports behavioral transparency rather than being pure 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?

For a complex retrieval tool with no output schema, the description explains what results contain (verbatim text, provenance, activation path, convergence), how it differs from siblings, and what safety profile the annotations already guarantee. Nothing essential for correct selection or invocation is missing.

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 schema already documents query, k, and sensitivity including enum meanings. The description does not add meaningfully beyond the schema for any parameter, making the baseline 3 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?

States a specific search verb and scope: semantic/associative search over the public sealed record and published site corpus. It distinguishes itself explicitly from search_sealed_forecasts and explains the meaning-based retrieval behavior with a concrete example.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Names the alternative search_sealed_forecasts and gives the condition that selects this tool: fuzzy/conceptual queries. It also provides the REST twin endpoint and enough context about sensitivity postures to guide invocation.

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

All JYOTINT Sealed Forecasts 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?