Skip to main content
Glama

Remedies for one graha

astroway_vedic_remedies_by_graha
Read-onlyIdempotent

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.
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
nameNo
grahaNo
doshasNo
grahaIdNo
remediesNo
sanskritNo
basisNoteNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds real behavioral context beyond that: it defines the shape of what comes back, notes that `doshas` cross-references this graha, and documents the credit cost tier. It stops short of stating ordering, completeness of coverage per type, or caching behavior.

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 and the required key, then a dense but purposeful payload list. The enumeration is long but each item tells the agent what data is available; the trailing group/endpoint/required/cost block is boilerplate but short.

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?

For a 4-parameter, read-only reference lookup with a full output schema and complete annotation coverage, the description gives enough to call it correctly and to anticipate the response. The only real omission is routing guidance against the three closely related remedies siblings.

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 the baseline is 3. The description restates the `graha` enum values (already in the schema enum) and labels `type` an optional filter without adding semantics beyond the schema's own comma-list explanation; `fields` and `precision` compact-mode parameters are not mentioned at all.

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?

Specific verb+resource: it returns the set of Vedic remedies keyed to a single graha, and it enumerates the concrete payload (BPHS japa count, beeja mantra, graha shanti components, dakshina, rudraksha mukhi, yantra, fasting day, gemstone/Lal Kitab links). That enumeration clearly separates it from siblings like astroway_vedic_remedies_by_dosha, astroway_vedic_remedies_by_type and astroway_vedic_remedies_catalogue.

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?

The description implies usage (look up remedies for a named planet) and flags that `type` is an optional narrowing filter, but it never states when to prefer this over the by_dosha, by_type or catalogue siblings, nor whether remedies_chart is a richer alternative. Guidance is inferable rather than explicit.

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