Skip to main content
Glama

Supastro

Read the year ahead for a birth chart

get_year_ahead
Read-onlyIdempotent

Calculates the coming twelve months for a birth chart: the Varshaphal (Tajika annual chart) in force, with the solar return moment, the Varsha Lagna, the Muntha and the lord of the year; the Vimshottari periods running now and every sub-period change in the year; and Jupiter's and Saturn's stays with the houses they transit and their Ashtakavarga points, month by month. Use it when someone asks about their year ahead, their Varshaphal or solar return, their Muntha, or what changes for them over the next year.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "birth_date": "<birth_date>",
      "birth_time": "<birth_time>",
      "birth_place": "<birth_place>"
    },
    "name": "get_year_ahead"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeNoOptional. Latitude of the birth place in decimal degrees, north positive. Give it only together with longitude, when the user supplied coordinates or the place could not be found by name.
longitudeNoOptional. Longitude of the birth place in decimal degrees, east positive. Give it only together with latitude.
birth_dateYesDate of birth as YYYY-MM-DD, for example 1990-01-15 for 15 January 1990. People write dates in different orders: day first in India and most countries, month first in the United States. Convert what the person wrote to YYYY-MM-DD yourself. If an all-number date could be read two ways, such as 05-06-1990, ask which number is the day before calling; never assume.
birth_timeYesLocal clock time of birth at the birth place, 24-hour HH:MM, for example 10:30, or 16:26 for 4:26 PM. If the person gave an hour from 1 to 12 without AM or PM, ask which before calling. Ask the user if the time is unknown; do not guess it.
birth_placeYesCity and country of birth, for example "Mumbai, India".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered structurally. The description's added value is the scope of the computed output, which is genuine but purely content-level. It says nothing about error behavior (e.g., unresolvable birth place), latency, or how to handle ambiguity beyond what the schema already prescribes, so a 3 is appropriate with annotations carrying the behavioral load.

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?

Two sentences, front-loaded with the verb 'Calculates' and the time horizon, followed by a compact enumeration of outputs and then usage triggers. The mid-sentence list is dense but every item is a concrete deliverable, not filler. Slightly long in the enumeration, but nothing is wasteful.

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?

There is no output schema, so the description must carry the burden of explaining what comes back, and it does so by enumerating the report's sections. Inputs are fully specified in the schema. The only gap is that the shape/format of the returned year-ahead digest (structured sections vs. prose) is not conveyed, though the content coverage is sufficient to choose and call the tool.

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% and the schema itself contains detailed disambiguation instructions (date-order ambiguity, AM/PM, when to supply latitude/longitude), so the schema does the heavy lifting. The description adds no parameter-level guidance of its own. Baseline 3 applies when the schema fully documents all five parameters.

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 names a specific computation and enumerates its contents precisely: Varshaphal/solar return, Varsha Lagna, Muntha, lord of the year, Vimshottari periods, and Jupiter/Saturn transits with Ashtakavarga points. An agent can tell this is the annual-chart report rather than a natal chart or generic transit tool. It stops short of explicitly contrasting with close siblings such as get_personal_transits or get_dasha_timeline, so it is clear but not fully differentiated.

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 second sentence gives explicit triggers: questions about the year ahead, Varshaphal or solar return, Muntha, or what changes over the next year. That is solid positive guidance. It does not state when NOT to use it or name an alternative for narrower needs (e.g., a single dasha lookup or one planet's transit), leaving overlap resolution to the agent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources