Skip to main content
Glama

JYOTINT Sealed Forecasts

by com.jyotishintelligence

ask_the_record

Ask any question about JYOTINT / Vijay Jyotish and get back the most relevant VERBATIM passages of the operator's own published site copy — never generated, never paraphrased, so it cannot hallucinate. This is the operator answering in his own words, drawn only from the public record (method, doctrine, the five pillars, mission-assurance fit, objections, pricing, heritage, etc.). Prefer this for any 'what does JYOTINT say about X' / 'why' / 'how does it work' question. Each passage cites its source page. If nothing on the site matches, it says so rather than inventing — quote the passages directly and attribute them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax passages (default 3, max 6).
queryYesThe question, in natural language.

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description fully discloses behavioral traits: it returns verbatim passages (never generated/paraphrased), cites source pages, and reports lack of matches truthfully. It does not cover authorization or rate limits, but for a read-only tool, this is sufficient.

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 paragraph that packs essential information: purpose, behavior, usage guidance, and fallback behavior. It is front-loaded with the core action and adds necessary details without excessive verbosity. Minor redundancy exists but does not detract significantly.

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 no output schema, the description adequately explains the return format (verbatim passages with source citations) and fallback behavior. It covers the tool's scope and limitations, making it complete for a retrieval Q&A tool without needing an output schema.

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% (both 'query' and 'limit' have descriptions). The description adds minimal extra meaning beyond the schema: it reinforces that 'query' is natural language and 'limit' defaults to 3 with max 6. The baseline of 3 is appropriate given full schema coverage.

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 clearly specifies the tool's purpose: answering questions about JYOTINT by retrieving verbatim passages from the operator's published site copy. It distinguishes itself from sibling tools by emphasizing that outputs are never generated or paraphrased, preventing hallucination.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use the tool ('Prefer this for any 'what does JYOTINT say about X' / 'why' / 'how does it work' question'), including behavior when no match is found. It does not explicitly mention alternatives or when-not-to-use, but the context is clear.

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