Skip to main content
Glama
@vedika-io/mcp-server

@vedika-io/mcp-server

Official
by vedika-io

vedika_health_ayurvedic

Analyze birth chart planetary positions to identify Ayurvedic dosha constitution, vulnerable body areas, diet, lifestyle, herbs, and seasonal recommendations.

Instructions

Ayurvedic constitution (Prakriti) analysis derived from birth chart. Maps planetary positions to the three doshas: Vata (air+ether, governed by Saturn and Rahu), Pitta (fire+water, governed by Sun and Mars), and Kapha (earth+water, governed by Moon and Jupiter). Returns dominant dosha, sub-dosha balance, vulnerable body areas based on 6th/8th house lords, recommended diet type, lifestyle adjustments, favorable seasons, and Ayurvedic herbs aligned with the chart. Based on Brihat Samhita and Charaka Samhita cross-references. Cost: $0.024/call.

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": {
      "datetime": "<datetime>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "timezone": "<timezone>"
    },
    "name": "vedika_health_ayurvedic"
  }
}

Input Schema

NameRequiredDescriptionDefault
ayanamsaNoSidereal zodiac correction. Default: lahiri. Only for Vedic calculations.
datetimeYesBirth date and time in ISO 8601 format, e.g. "1990-06-15T14:30:00". Required for all chart calculations.
latitudeYesBirth location latitude (-90 to 90). Polar latitudes >66.5 are rejected (house calculations unreliable).
timezoneYesTimezone as UTC offset "+05:30" or IANA "Asia/Kolkata". UTC offsets preferred.
longitudeYesBirth location longitude (-180 to 180).
includeRemediesNoInclude dietary and lifestyle recommendations. Default: true.
includeSeasonalNoInclude seasonal (Ritucharya) recommendations. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.9

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries full burden: it does disclose the returned fields, the classical source texts, and a per-call cost of $0.024, which is genuinely useful. It omits auth requirements, whether the call is purely computed vs stored, failure modes, and whether remedial output changes the response shape.

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?

Purpose is front-loaded, followed by return contents, sourcing, and cost. The planetary-governor parenthetical ('Vata... governed by Saturn and Rahu') is decorative detail that consumes space without helping an agent invoke the tool.

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?

No output schema exists, and the description does enumerate the return payload in enough detail for an agent to know what it gets back. Input requirements are handled by the fully documented schema, so the only residual gap is sibling disambiguation.

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 schema already documents all seven parameters including the ayanamsa enum and the includeRemedies/includeSeasonal flags. The description's mention of 'recommended diet type, lifestyle adjustments, favorable seasons' implicitly maps to those two boolean flags but never says they are gated by them, adding no real semantics beyond the schema.

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 verb and resource: 'Ayurvedic constitution (Prakriti) analysis derived from birth chart', and enumerates the exact outputs (dominant dosha, sub-dosha balance, vulnerable areas, diet type). However, it never distinguishes itself from the closely named sibling 'vedika_doshas', which an agent will likely confuse with this tool.

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

Usage Guidelines2/5

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

No statement of when to use this tool versus 'vedika_doshas', 'vedika_birth_chart', or 'vedika_dasha'. The only contextual cue is the price line, and there is no indication of prerequisites (e.g. that a birth chart input is required rather than a chart ID).

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