Skip to main content
Glama

Remedies catalogue (upaya)

astroway_vedic_remedies_catalogue
Read-onlyIdempotent

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.
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
typesNo
doshasNo
grahasNo
sourcesNo
basisNoteNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description goes beyond them by disclosing the response model (grouped under grahas and doshas, items carrying `source` and a `classical`/`modern-popular` `basis`), which tells the agent how to cite and qualify results; it omits catalogue size and pagination 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?

Roughly three sentences, front-loaded with what the catalogue contains, then the filter, then the no-chart note. The enumeration of ten remedy types largely duplicates the schema's own list, which is the only wasted space; everything else earns its place.

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?

With an output schema present, return values need no explanation, and the description still supplies the semantic distinction that the schema cannot (classical vs modern-popular provenance). The one gap is that it does not tell the agent when to prefer the graha-, dosha- or type-scoped siblings over this full catalogue.

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 the schema already documents `type`, `fields` and `precision` including the comma-list form and the 0-15 precision range. The description restates the comma-list behavior for `type` and adds nothing about `fields` or `precision`, so it does not exceed the schema baseline.

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 names a concrete resource and its contents precisely: the full remedies catalogue covering nine grahas and eight doshas, with items tagged by type and by `basis`. It also implicitly separates itself from chart-dependent siblings via 'static lookup, no chart needed', though it never names `vedic_remedies_by_graha`, `by_dosha`, `by_type` or `remedies_chart`, so an agent must infer the split from those sibling names.

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' and 'Optional `type` filter' give real usage context: no birth data is required and narrowing is optional. However, no when-not guidance or alternative routing is provided, which matters here because four sibling tools cover remedies and `by_type` overlaps directly with this tool's `type` filter.

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