Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Remedies catalogue (upaya)

astroway_vedic_remedies_catalogue
Read-onlyIdempotent

Retrieve classical and popular Vedic remedies for the nine grahas and eight doshas by type—mantra, puja, gemstone, and more—with cited source and classical or modern basis; filter by remedy type.

Instructions

The whole remedies catalogue: for each of the nine grahas and eight doshas, the classical and popular remedies by type (mantra, puja, deity, yantra, rudraksha, fasting, charity, colour, gemstone, lal-kitab). Each item names its source and a basis: classical when the cited text has it, modern-popular otherwise. Optional type filter, one value or a comma list. Static lookup, no chart needed.

[Group: Vedic] [Endpoint: GET /v1/vedic/remedies/catalogue] [Cost: 5 credits (Tier ½)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_vedic_remedies_catalogue"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
typesNo
doshasNo
grahasNo
sourcesNo
basisNoteNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.1

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, and closed-world behavior, so the safety profile is covered. The description adds genuinely new context: it is a static lookup requiring no chart, and it defines what `basis: classical` versus `modern-popular` means, which matters for interpreting results. It does not cover pagination or catalogue size, which keeps it from 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?

Front-loaded with the resource and scope, then item semantics, then the filter, then the no-chart constraint. Every sentence carries information and there is no filler.

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?

For a single optional parameter, static lookup tool with an output schema present, the description covers scope, item structure, filter behavior, and the key interpretive field (`basis`). Nothing an agent needs 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 description coverage is 100% and the single `type` parameter already enumerates all valid values and states that all types are returned when omitted. The description restates the same value list and the comma-list behavior, adding little beyond the schema, so the baseline of 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?

The description states a specific resource (the whole remedies catalogue) and its scope: nine grahas, eight doshas, and eleven remedy types, with per-item `source` and `basis`. 'The whole remedies catalogue' and 'no chart needed' separate it from the per-graha, per-dosha, and chart-based siblings. It stops short of 5 because it offers a `type` filter while a sibling named `astroway_vedic_remedies_by_type` exists, and the description never addresses that overlap.

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?

'Static lookup, no chart needed' implies when this applies: browsing the full catalogue without chart input. However, no explicit when-to-use or when-not guidance is given against the closely related `remedies_by_type`, `remedies_by_graha`, and `remedies_by_dosha` tools, so an agent must infer which to pick.

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