Skip to main content
Glama

JYOTINT Sealed Forecasts

by com.jyotishintelligence

get_information_yield

Information Yield (IY) — how much a confirmed call should move a skeptic's belief, in BITS of surprise-if-true (log2 of the published 1-in-N prior, capped at 1-in-a-million; earned = surprise × verdict-credit). A base rate / consensus-follower scores ZERO bits by construction — the metric on which the 'a base rate ties the Brier' objection inverts. Returns the corpus summary (median ≈6.8 bits/call + %earned), the launch/intel/combined domain split, and the count. Pass an optional id for one call's bits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOptional advisory id (e.g. 'LA-022') for one call's IY.

TDQS

B3/5.0
Behavior2/5

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

No annotations provided, and the description does not explicitly state that the tool is read-only or disclose other behavioral traits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose with a lengthy definition of IY that could be shortened, making it less concise.

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?

Given the simple input (one optional parameter) and lack of output schema, the description adequately describes what is returned, including specifics about corpus summary and domain splits.

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?

The description adds context to the optional 'id' parameter beyond the schema, explaining it retrieves bits for a single call.

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 states what the tool returns (corpus summary and optionally one call's bits), effectively conveying the purpose despite some verbose definition.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like get_corpus_insights or get_advisory.

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 toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation4/5

Most tools have clearly distinct purposes (fetch one forecast vs. list open calls vs. search), but neural_search and search_sealed_forecasts both retrieve from the same corpus, and ask_the_record overlaps slightly with neural_search for site-copy questions. Descriptions mitigate ambiguity, but a few boundaries require careful reading.

Naming Consistency4/5

The dominant pattern is get_<noun> (get_advisory, get_map, get_luck_test), with list_open_calls, search_sealed_forecasts, ask_the_record, and neural_search as deviations. All names are lowercase snake_case and readable, but the verb prefixes are not perfectly uniform.

Tool Count5/5

With 13 tools, the server is well-scoped for a specialized sealed-forecast corpus. Each tool addresses a distinct analytical or retrieval need, and the count fits comfortably in the ideal range without feeling bloated or thin.

Completeness5/5

The tool surface covers the full lifecycle of interacting with the corpus: search, retrieve, list, inspect stats, verify integrity, regrade, visualize, and ask questions. The append-only nature means no update/delete tools are needed, so the set is complete for its stated purpose.

Resources