Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_numerologynumbers

Returns numerology numbers calculated from a person's full name and birth date via the AstroChalit API.

Instructions

Execute numerologyNumbers 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_numerologynumbers"
  }
}

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 supplied, so the description carries the full behavioral burden, and it discloses nothing: no indication of side effects, authentication requirements, rate limits, idempotency, or what the response contains. 'Execute ... API' conveys only that a remote call occurs, which is already implicit in every tool.

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 description is a single six-word fragment with zero waste but also zero useful content; brevity here comes from under-specification rather than disciplined writing. There is no front-loaded statement of outcome or scope.

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?

With no annotations and no output schema, the description is the only place an agent could learn what this domain calculation returns (e.g., life path, destiny, or birth numbers) and in what shape, and it says nothing. For a domain-specific calculation tool consuming a name and birth date, this leaves a real gap.

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 all three parameters (fullName, dateOfBirth, gender) documented including format examples and an enum, so the schema does the heavy lifting. The description contributes no additional parameter meaning, which meets the baseline for high-coverage schemas but no more.

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 phrase 'Execute numerologyNumbers AstroChalit API' essentially restates the tool name and vendor, adding only the vague verb 'Execute'. It never states what the tool actually produces (numerology numbers derived from name and birth date) or how it differs from any sibling. An agent learns almost nothing it could not infer from the name alone.

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 mention of alternatives among the many astrology siblings (get_ashtakoot, get_biorhythm, get_gemstone_suggestion, etc.), and no prerequisites. The word 'Execute' implies a call but gives no context for choosing this tool over another.

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