Skip to main content
Glama

JYOTINT Sealed Forecasts

by com.jyotishintelligence

get_warning_timeline

The 'before-the-event' indications-and-warning / after-action timeline for a named event, by advisory id (e.g. 'LA-022') or slug (e.g. 'new-glenn-ng3', 'crocus'). A neutral chronology: the official/authoritative source named FIRST, then the dated, hash-anchored JYOTINT sealed call as one independently-verifiable entry, with what it does and does not establish. Use for 'what dated public warnings preceded [event]'. Omit id to list every available timeline.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAdvisory id or timeline slug. Omit to list all.

TDQS

A4.3/5.0
Behavior4/5

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

Discloses that the timeline is neutral, with official source first, then JYOTINT sealed call, and mentions what it does and does not establish. Since no annotations exist, this is good transparency.

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 informative without being overly long, but could be slightly more concise. It front-loads the main purpose and then adds necessary details.

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?

Despite no output schema, the description explains the response structure (official source first, then hash-anchored call) and includes what entries do and don't establish. This is sufficient for a simple single-parameter tool.

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. The description adds examples ('LA-022', 'new-glenn-ng3') and clarifies the id parameter accepts advisory id or slug, adding value beyond the schema description.

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 states the tool retrieves a 'before-the-event' or after-action timeline for a named event, using advisory id or slug. It uses specific verbs and resource, distinguishing it from siblings like get_advisory which provides the advisory text itself.

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?

Provides explicit usage: 'Use for what dated public warnings preceded [event]. Omit id to list every available timeline.' It gives context but doesn't explicitly state when not to use or mention alternatives.

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