Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_numerology_prediction

Calculates numerology predictions from a person's full name and date of birth, with optional gender, to deliver personalized Vedic numerology insights via the AstroChalit API.

Instructions

Execute numerology_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_numerology_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

D1.9/5.0
Behavior1/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, and it says nothing: no note on read-only vs. mutation, authentication needs, rate limits, or what the response contains. 'Execute ... API' conveys no behavioral context.

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

Conciseness3/5

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

The definition is one short sentence with no padding, so nothing is wasted. However, it is under-specified rather than concise, and the 'AstroChalit' naming is noise for an agent.

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?

For a three-parameter domain-prediction tool with no annotations and no output schema, the description should explain what the prediction covers and what comes back. After the name and the schema, almost nothing an agent needs in order to choose or trust this tool is present.

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%, with fullName, dateOfBirth, and gender each documented in the schema, including the YYYY-MM-DD format and the enum for gender. The description adds no parameter meaning beyond the schema, but the baseline of 3 applies when the schema does the heavy lifting.

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 only restates the tool name in imperative form ('Execute numerology_prediction AstroChalit API'), giving the resource but not what a numerology prediction entails or how it differs from sibling tools like get_lifepath_prediction. Beyond the name, the only added information is that a third-party AstroChalit API is called.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no distinction from the many other prediction/chart siblings, and no exclusions or prerequisites. An agent has to infer everything about selection from the name alone.

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