Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_lifepath_prediction

Generate a Vedic astrology life-path prediction from a person's full name and date of birth using the AstroChalit API.

Instructions

Execute lifepath_prediction AstroChalit API

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": {
      "fullName": "<fullName>",
      "dateOfBirth": "<dateOfBirth>"
    },
    "name": "get_lifepath_prediction"
  }
}

Input Schema

NameRequiredDescriptionDefault
genderNoGender of the personMale
fullNameYesFull name of the person
dateOfBirthYesDate of birth in YYYY-MM-DD format (e.g. 1995-05-15)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

C2/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It doesn't mention authentication or API-key requirements for the external service, latency, error behavior, or what the prediction output looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single phrase is technically brief with no filler, but brevity here comes from under-specification rather than economy. There is no front-loaded statement of purpose, scope, or result.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a prediction endpoint with no output schema and no annotations, so the description needed to explain what comes back and any prerequisites. It supplies neither, leaving an agent unable to predict the response shape or whether setup (e.g., API credentials) is needed.

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 descriptions and an enum for gender and an explicit date format example for dateOfBirth, so the schema already explains every parameter. The description adds no meaning beyond it, but the baseline of 3 applies when structured fields do the work.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description essentially restates the tool name: "Execute lifepath_prediction AstroChalit API" adds only the fact that it calls an external AstroChalit API. It does not state what a lifepath prediction is, what it returns, or how it differs from siblings like get_numerology_prediction.

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?

There is no guidance on when to use this tool versus alternatives. The sibling list includes several prediction-style tools (numerology, radical, biorhythm), yet nothing explains which input or user intent should route to lifepath prediction.

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