JYOTINT Sealed Forecasts

search_sealed_forecasts

Read-onlyIdempotent

Search the JYOTINT sealed-forecast corpus (Bitcoin-anchored, dated-before-the-event predictions) by free text across id, title, and the verbatim sealed claim. Returns matching records with their grade, sealed probability, seal date, source artifact, and SHA-256 seal hash. For fuzzy or conceptual queries, use neural_search (finds calls by MEANING; REST twin GET /brain?q=…).

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Max results (default 10).
`query`	Yes	Free-text query (e.g. 'Crocus', 'NISAR', 'Brazil election', 'recession').
`graded_only`	No	Restrict to graded (Brier) records. Default false.
`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"
+}

First observedJul 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the bar is low, and the description adds real substance beyond them: the returned fields (grade, sealed probability, seal date, source artifact, SHA-256 seal hash) and the `withheld` behavior under high_precision sensitivity. Minor gap: no note on pagination or result ordering.

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?

Three sentences, each earning its place, with the core purpose front-loaded and the alternative route at the end. The parenthetical about the REST twin is slightly extra but still informative.

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?

No output schema exists, but the description compensates by listing the key return fields. Combined with explicit alternative routing and annotation-covered safety, an agent has nearly everything needed; only pagination/ordering behavior is unstated.

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%, so baseline is 3, but the description adds meaning the schema does not: which fields the `query` actually matches against (id, title, verbatim claim). That scope detail is genuinely useful for forming a query.

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 verb (Search) and resource (the JYOTINT sealed-forecast corpus) plus the exact fields scanned (id, title, verbatim sealed claim), and it names the sibling it is not (neural_search for meaning-based lookups). An agent can distinguish it from neural_search without opening either schema.

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?

Explicitly routes fuzzy/conceptual queries to neural_search and even names its REST twin (GET /brain?q=…), while this tool handles free-text literal matching. The when-to-use-this-vs-alternative decision is fully stated.

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?