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

@vedika-io/mcp-server

Official
by vedika-io

vedika_spiritual_mantra

Get personalized Vedic mantra recommendations from birth chart analysis, identifying weak planets and returning Sanskrit mantras with japa count, timing, direction, and mala guidance.

Instructions

Get personalized mantra recommendations based on birth chart analysis. Identifies weak or afflicted planets and recommends Vedic mantras from classical texts (Mantra Mahodadhi, BPHS remedies chapter). Returns the mantra in Sanskrit (Devanagari + IAST transliteration), the specific planet or deity it addresses, recommended repetition count (japa sankhya), best time to chant (muhurta), direction to face, and associated rosary (mala) material. Can also return mantras for specific purposes like career, health, or relationships. Cost: $0.016/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_spiritual_mantra"
  }
}

Input Schema

NameRequiredDescriptionDefault
planetNoSpecific planet to get mantras for, regardless of chart weakness. E.g., saturn for Shani mantra.
purposeNoPurpose for the mantra recommendation. If omitted, derives from weakest chart planet.
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.9

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it enumerates the returned fields (Devanagari + IAST, japa sankhya, muhurta, direction, mala material) and discloses per-call cost ($0.016/call). It stops short of noting auth requirements or failure modes for invalid birth data.

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 capability followed by return contents, an alternate mode, and pricing — all actionable. Slightly dense at four sentences but nothing is padding.

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, yet the description explicitly lists every returned field, which compensates well. For a 7-parameter, 4-required chart-based tool the only gap is the absence of any guidance on error handling for polar latitudes or invalid datetime.

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% with three enums, so the schema already documents all seven parameters thoroughly. The description adds only light reinforcement (chart-weakness defaulting, purpose-based overrides) rather than new syntax or format meaning, 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?

Specific verb + resource ('Get personalized mantra recommendations based on birth chart analysis') plus concrete sourcing of the mantras (Mantra Mahodadhi, BPHS remedies). It does not explicitly distinguish itself from nearby siblings such as vedika_lalkitab_remedies or vedika_spiritual_deity, so an agent must infer the boundary.

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?

Usage is implied: 'Can also return mantras for specific purposes like career, health, or relationships' signals the purpose-driven mode, and the planet parameter covers the targeted mode. However, there is no explicit when-to-use guidance or exclusion versus the remedy/deity siblings.

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