Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Remedies for one graha

astroway_vedic_remedies_by_graha
Read-onlyIdempotent

Retrieve Vedic remedies for a chosen graha, including mantra, japa count, yantra, rudraksha, fasting and charity guidance. Filter by remedy type to find planet-specific spiritual practices.

Instructions

Remedies of one graha (graha: sun, moon, mars, mercury, jupiter, venus, saturn, rahu, ketu): the Vedic mantra with its BPHS japa count, the beeja mantra, the graha shanti (image material, contemplation, samidh, food), dakshina, colour and weekday, rudraksha mukhi, yantra, fasting day, and links to the gemstone and Lal Kitab routes. doshas lists the doshas that draw on this graha. Optional type filter.

[Group: Vedic] [Endpoint: GET /v1/vedic/remedies/by-graha] [Required: graha] [Cost: 5 credits (Tier ½)]

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": {
      "graha": "<graha>"
    },
    "name": "astroway_vedic_remedies_by_graha"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoRemedy type, or a comma list of them: mantra, puja, deity, yantra, rudraksha, fasting, charity, colour, gemstone, lal-kitab. All types when omitted.
grahaYesThe graha, lowercase English name.

Output Schema

NameRequiredDescriptionDefault
nameNo
grahaNo
doshasNo
grahaIdNo
remediesNo
sanskritNo
basisNoteNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world, non-destructive), and the description adds operationally relevant detail they don't: the GET endpoint, the required graha, and a 5-credit cost tier. It also discloses that omitting `type` returns all remedy types, which sets expectations about result size. It does not discuss error behavior for an invalid graha beyond the enum.

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 subject and the resource, then a dense enumeration of returned content, then the filter and the doshas note. The long list sentence is packed but every element is informative. The trailing metadata block (group, endpoint, required, cost) is structured rather than prose waste.

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?

With an output schema present, return values need no prose explanation, and the description still tells the agent what categories of remedy appear plus the credit cost and required input. For a two-parameter read tool with full annotation and schema coverage, nothing needed to call it correctly is missing.

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 coverage is 100%, so both parameters are already fully documented, including the enum of nine grahas and the comma-list semantics of `type`. The description restates the optional type filter and the all-types default without adding syntax or behavioral detail beyond the schema. Baseline 3 applies.

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 resource and scope: remedies for exactly one graha, and enumerates the payload (mantra with BPHS japa count, beeja mantra, graha shanti components, dakshina, colour, weekday, rudraksha mukhi, yantra, fasting day, gemstone/Lal Kitab links). An agent knows precisely what comes back. It stops short of naming the sibling routes (remedies_by_type, remedies_by_dosha) so the caller must infer which of the three access paths to pick.

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

Usage Guidelines3/5

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

Usage is only implied: the graha-first index plus 'Optional `type` filter' signals a per-planet lookup with a narrowing option, and the note that `doshas` names doshas drawing on this graha hints at a bridge to remedies_by_dosha. There is no explicit when-to-use or when-not statement, and no direction to remedies_by_type for type-first enumeration.

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

Deploy Server

Other Tools