Asterwise

Gemstone Recommendations

asterwise_get_gemstone_recommendations

Read-onlyIdempotent

Computes Ratna-style gemstone picks and cautions from the natal chart. Returns the primary and role-based stones, secondary options, contraindications and a safety note.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm chart before wearing advice. AFTER: asterwise_get_remedies — broader remedial programme if needed.

INPUT CONTRACT: BirthData follows the global contract.

DO NOT CONFUSE WITH: asterwise_get_remedies — mantras, fasting, charity rows, not a gem matrix. asterwise_get_lal_kitab_remedies — Lal Kitab actions, not classical Ratna picks.

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

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": "<birth>"
    },
    "name": "asterwise_get_gemstone_recommendations"
  }
}

Input Schema

Name	Required	Description	Default
`birth`	Yes	Birth data for tools that need the exact birth time (no sunrise fallback).
`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.

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / birth / description

Previous value: -"Birth data for tools that need the exact birth time.\n\nTheir API endpoints have no sunrise fallback and reject a request without\na time, so the time is required here instead of failing upstream."New value: +"Birth data for tools that need the exact birth time (no sunrise fallback)."

Changed7 schema fields changedOct 6, 2026

changedInput schema / properties / birth / description

Previous value: -"Birth data for a single person."New value: +"Birth data for tools that need the exact birth time.\n\nTheir API endpoints have no sunrise fallback and reject a request without\na time, so the time is required here instead of failing upstream."

removedInput schema / properties / birth / properties / time / anyOf

Removed value: -[
-  {
-    "pattern": "^\\d{2}:\\d{2}$",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / birth / properties / time / default
```
Removed value: -null
```

changedInput schema / properties / birth / properties / time / description

Previous value: -"Birth time HH:MM (24h), e.g. '06:45'. Omit if unknown (a sunrise chart is used and birth_time_provided=false); never pass '00:00' for unknown."New value: +"Birth time HH:MM (24h), e.g. '06:45'. Required: this tool has no sunrise fallback. If the user doesn't know it, say so rather than guessing; never pass '00:00' for unknown."

addedInput schema / properties / birth / properties / time / pattern
```
Added value: +"^\\d{2}:\\d{2}$"
```
addedInput schema / properties / birth / properties / time / type
```
Added value: +"string"
```

changedInput schema / properties / birth / required

Previous value: -[
-  "date",
-  "lat",
-  "lon"
-]New value: +[
+  "date",
+  "time",
+  "lat",
+  "lon"
+]

First observedSep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered and the bar is lower. The description still adds value by disclosing that output includes contraindications and a safety note, and that wearing advice presupposes a confirmed chart — meaningful context for a recommendation tool that could be misused.

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?

Front-loaded with the core purpose, then clearly labeled WORKFLOW / INPUT CONTRACT / DO NOT CONFUSE blocks that are easy to scan. Slightly longer than needed because the docs URL and output listing duplicate coverage available in the output schema.

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?

Given an output schema exists, the description need not explain return values, yet it summarizes them briefly and adds a route to the full output/error contract. Workflow, prerequisites, sibling disambiguation and data contract are all present for a single-required-parameter read 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%, with nested BirthData fields fully documented (including the explicit no-sunrise-fallback rule for 'time'), so the schema carries parameter semantics. The description only adds a pointer that BirthData follows the global contract, which is orientation rather than new per-parameter meaning.

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 ('Computes Ratna-style gemstone picks and cautions from the natal chart') and names the returned artifacts. The DO NOT CONFUSE section explicitly separates it from asterwise_get_remedies and asterwise_get_lal_kitab_remedies, so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides an explicit BEFORE/AFTER workflow (confirm chart via asterwise_get_natal_chart, follow up with asterwise_get_remedies) plus two named alternatives with the condition that selects each. When-to-use and when-not-to-use are both covered directly.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.