Asterwise

Nakshatra Details

asterwise_get_nakshatra_details

Read-onlyIdempotent

Looks up static metadata for one of twenty-seven nakshatras by name and returns interpretive, professional, activity, and body-map reference data.

WORKFLOW: BEFORE: None — this tool is standalone. AFTER: None.

INPUT CONTRACT: nakshatra_name is sent as given; the API ignores case, spaces, hyphens and common romanisation differences ('uttarashadha', 'Aswini', 'Moola' and 'Krithika' all match). An unknown name returns 404 with the 27 valid names and, for a near miss, a suggestion.

DO NOT CONFUSE WITH: asterwise_get_natal_chart — computes birth nakshatra from time/place, not encyclopaedic copy. asterwise_get_dasha — uses Moon nakshatra for timing, not this lookup table.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-nakshatra-details/

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": {
      "nakshatra_name": "<nakshatra_name>"
    },
    "name": "asterwise_get_nakshatra_details"
  }
}

Input Schema

Name	Required	Description	Default
`nakshatra_name`	Yes	Nakshatra name, e.g. 'Rohini' or 'Uttara Phalguni'.
`response_format`	No	Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.	markdown

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 5, 2026

addedInput schema / properties / nakshatra_name / description

Added value: +"Nakshatra name, e.g. 'Rohini' or 'Uttara Phalguni'."

addedInput schema / properties / response_format / description

Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."

Changed2 schema fields changedSep 4, 2026

addedInput schema / properties / response_format / default
```
Added value: +"markdown"
```

changedInput schema / required

Previous value: -[
-  "nakshatra_name",
-  "response_format"
-]New value: +[
+  "nakshatra_name"
+]

First observedApr 22, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already cover read-only, idempotent, closed-world and non-destructive traits, and the description goes further: it documents input normalization (case, spaces, hyphens, romanisation variants), the exact failure mode (404 listing the 27 valid names), and near-miss suggestions. That is behavioral detail beyond what annotations carry.

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?

Front-loaded purpose sentence followed by clearly labelled WORKFLOW, INPUT CONTRACT and DO NOT CONFUSE sections. No redundant restatement of the name or title, and the docs link is a compact pointer to the full contract.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be described; the description instead covers the error contract, matching semantics, and routing against siblings. For a two-parameter read-only lookup this is complete enough to invoke correctly.

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% and the enum for response_format is self-explanatory, so the baseline would be 3. The description adds real value by explaining the accepted name variants and matching behavior ('Moola', 'Krithika', hyphens/spaces ignored), which the schema's short example does not convey.

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 precise verb ('looks up') and resource ('static metadata for one of twenty-seven nakshatras by name') and enumerates the returned data categories. The DO NOT CONFUSE section distinguishes it explicitly from get_natal_chart and get_dasha, so an agent can differentiate it from siblings.

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?

Explicitly declares the tool is standalone with BEFORE/AFTER None, and names two sibling tools it should not be confused with, including the reason for each. It does not, however, contrast against the closest sibling, get_nakshatra_prediction, which is the more plausible confusion.

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

All Asterwise tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?