Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_numerologyreport

Generates a numerology report from a person's full name and date of birth, with optional gender, for Vedic astrology analysis via AstroChalit.

Instructions

Execute numerologyReport 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_numerologyreport"
  }
}

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/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: not whether the call is read-only or has side effects, not whether it is an external/third-party call ("AstroChalit API" hints at one but does not say), not latency/rate limits, and not what kind of result comes back. Only the bare fact that an external API is executed is conveyed.

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?

Five words with no filler, so nothing is wasted, but the fragment is under-specified rather than genuinely concise and is not front-loaded with any actionable context such as output shape or constraints.

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 report generator with no annotations and no output schema, the description leaves the agent unable to predict what the report contains or how to present it. The schema covers the inputs, but the behavioral and output side is entirely unaddressed.

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 (including an explicit YYYY-MM-DD example) and a gender enum all documented in the schema. The description adds no additional meaning about these parameters, so the baseline of 3 applies.

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

Purpose3/5

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

"Execute numerologyReport AstroChalit API" names a resource (numerology report) and a verb (execute), so an agent can infer it returns a numerology reading. However the phrasing is a wrapper-style fragment rather than a plain statement of purpose, and it gives no clue how a numerology report differs from sibling outputs like get_gemstone_suggestion or the divisional-chart tools.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent must infer from the name alone that this is the tool for numerology requests and not for compatibility or chart calculations.

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