Skip to main content
Glama

Supastro

Check how much the birth time matters

check_birth_time_sensitivity
Read-onlyIdempotent

Shows how sensitive a birth chart is to its birth time. It gives the exact clock window in which the rising sign held on the birth day and how far the stated time is from a change, then recalculates the chart for earlier and later birth times and lists what changes: the rising sign, the Navamsa rising sign, the Moon's nakshatra and pada, the Atmakaraka and the dates of the Vimshottari periods. Use it when someone is unsure of their exact birth time, asks whether a few minutes would change their chart, or wants to know which parts of their chart are safe to rely on.

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": "check_birth_time_sensitivity"
  }
}

Input Schema

NameRequiredDescriptionDefault
minutesNoOptional. The largest birth-time error to test, in minutes either way. Defaults to 30.
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral substance beyond that by disclosing exactly what is computed and which chart elements (rising sign, Navamsa lagna, Moon nakshatra/pada, Atmakaraka, Vimshottari period dates) are re-tested. It does not mention cost, latency, or what happens when no change occurs.

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

Conciseness5/5

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

Three sentences, front-loaded with the core purpose, then the output content, then the usage triggers. Every sentence carries distinct information and there is no redundant restatement of the title or schema.

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?

With no output schema, the description compensates by describing the return contents in prose (window, distance to change, list of changed elements), which is the key thing an agent needs. Annotations cover the safety profile and the schema covers all parameters, leaving only minor gaps such as the absence of an explicitly named alternative 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%, so all six parameters, including the minutes window and coordinate handling, are already documented in the schema. The description's mention of "earlier and later birth times" and "how far the stated time is from a change" loosely motivates the minutes parameter but adds no syntax or default information beyond the schema, so the baseline 3 applies.

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 and resource ("shows how sensitive a birth chart is to its birth time") and immediately enumerates the concrete outputs: the clock window for the rising sign, distance to a change, and the recalculated items. This is clearly distinct from siblings like cast_birth_chart or get_planet_positions, which produce charts rather than sensitivity analysis.

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?

Gives three explicit trigger conditions: unsure of exact birth time, asking whether a few minutes would change the chart, or wanting to know which parts are reliable. That is strong when-to-use guidance, but no when-not condition or named alternative (e.g. cast_birth_chart for a confirmed time) is offered.

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