Skip to main content
Glama

Remedies for one dosha

astroway_vedic_remedies_by_dosha
Read-onlyIdempotent

Remedies of one dosha (dosha: mangal, kaal-sarp, pitru, sade-sati, grahan, shrapit, guru-chandal, kemadruma). classicalStatus says whether the dosha itself is in the classical texts; specific holds the rites written for it or for its nearest classical trigger (BPHS 83 curses, BPHS 91 eclipse birth), each noting what it was written for; grahaRemedies holds the remedies of the grahas it is defined over; detection names the route that checks a chart for it. Optional type filter.

[Group: Vedic] [Endpoint: GET /v1/vedic/remedies/by-dosha] [Required: dosha] [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": {
      "dosha": "<dosha>"
    },
    "name": "astroway_vedic_remedies_by_dosha"
  }
}

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.
doshaYesThe dosha, lowercase and hyphenated.
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
doshaNo
grahasNo
relatedNo
specificNo
basisNoteNo
detectionNo
disclaimerNo
grahaRemediesNo
classicalStatusNo

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's contribution is output semantics: it explains that classicalStatus signals scriptural provenance, that specific contains rites for the dosha or its nearest classical trigger, and that detection names the chart-checking route. That is genuine meaning beyond the annotations, though it stops short of noting the 5-credit cost or any result-size considerations.

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?

The core statement ('Remedies of one dosha') is front-loaded, and the remaining clauses are tightly packed with field-level meaning rather than filler. The back half is dense with response-field jargon, but every sentence carries information an agent would otherwise have to infer from the output schema.

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, the description need not enumerate return values, and it correctly spends its words on explaining the semantics of the key response fields instead. Annotations plus 100% schema coverage handle the rest, leaving only minor gaps such as cost awareness and whether these are static reference remedies rather than chart-personalized ones.

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%, including the dosha enum and the full type list (mantra, puja, deity, ... comma lists), so the schema already carries the parameter meaning. The description restates the dosha enum and mentions the optional type filter without adding syntax, defaults, or interaction rules, so 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?

The description names a specific resource (remedies) scoped to exactly one dosha and enumerates the eight valid doshas, so an agent knows precisely what it retrieves. Sibling differentiation is implicit in the name ('by-dosha' versus remedies_by_graha, remedies_by_type, remedies_catalogue) but the description never states those alternatives, keeping it short of a 5.

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 only usage instruction is 'Optional `type` filter', which tells the agent a filter exists but not when it should be applied. There is no when-to-use vs when-to-use-an-alternative guidance, no prerequisite (e.g. must first detect the dosha via a dosha-check tool), and no exclusion criteria, so usage is only implied by the topic.

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