Skip to main content
Glama

Supastro

Check today's Moon strength for a birth

get_daily_moon_strength
Read-onlyIdempotent

Calculates how today's Moon sits against a person's birth Moon: the Tara Bala category (the Moon's nakshatra counted from the birth nakshatra), Chandra Bala (the Moon's sign counted from the birth Moon sign), and when Chandrashtama (Moon in the 8th sign from the birth Moon) is running or next begins. Use it when someone asks whether today is a good day for them, for their Tara Bala or Chandra Bala, or when their Chandrashtama falls. Returns the computed positions with the classical rule's own result for each. Covers this moment by default, or another date.

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_daily_moon_strength"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. The day to check as YYYY-MM-DD, read at 12:00 UTC. Defaults to this moment. Convert the person's own wording to this form; if an all-number date could be read two ways, ask which number is the day.
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.
time_zoneNoOptional. IANA time zone for the times shown, for example "Asia/Kolkata". Defaults to the birth place's time zone.
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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive closed-world behavior, so the safety profile is covered. The description adds real value on top: it discloses the output shape ("the computed positions with the classical rule's own result for each") and the default scope ("covers this moment by default, or another date"), which is not obvious for a date-parameterized tool. No permission or failure-mode caveats, so not a 5.

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 map cleanly onto what it computes, when to call it, and what it returns — no filler or restated title. The definition sentence is dense with domain terms but front-loads the operative concepts before the usage sentence.

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 and seven parameters, the description carries the burden of describing returns and it does so at the right level of abstraction for an agent to relay results. The 100%-covered schema handles parameter detail, so the only gap is the absence of any boundary drawn against sibling tools that also answer "is today good for me?".

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 every parameter — including the date/timezone/coordinate fallbacks and the day-first vs month-first date ambiguity — is documented in the schema itself. The description only adds the loose notion of evaluating "against a person's birth Moon" and a default-to-now note, which the schema largely covers. Baseline 3 is appropriate.

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?

States a specific verb (calculates) and a precisely bounded resource: today's Moon evaluated against a birth Moon, decomposed into three named quantities (Tara Bala, Chandra Bala, Chandrashtama). The Moon-only scope implicitly separates it from a general planet-strength tool, but it never names a sibling, so the differentiation is inferential rather than explicit.

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?

"Use it when someone asks whether today is a good day for them, for their Tara Bala or Chandra Bala, or when their Chandrashtama falls" gives concrete triggering phrasings an agent can pattern-match on. It does not state when NOT to use it or point to any alternative tool (e.g. for other planets or longer-range transits), so it stays short of the 5 bar.

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