Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_biorhythm

Calculate biorhythm cycles from a birth date (YYYY-MM-DD) through the AstroChalit API to support daily rhythm and astrology analysis.

Instructions

Execute biorhythm AstroChalit API

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_biorhythm"
  }
}

Input Schema

NameRequiredDescriptionDefault
dobNoDate of birth in YYYY-MM-DD format (e.g. 1995-05-15)
dateOfBirthNoAlternative date of birth in YYYY-MM-DD format

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 largely drops it. It does not state that this calls an external AstroChalit service, what it returns, whether either parameter is mandatory, or what happens if both date fields are supplied or neither is.

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?

It is a single short sentence with no wasted clauses, so it is front-loaded and easy to parse. Brevity here comes at the cost of substance rather than from efficient compression of useful information.

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 behavior and return semantics could be conveyed, and it says nothing about either. It is not adequate for a two-parameter tool whose parameters are mutually ambiguous.

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%, so the schema itself documents dob and dateOfBirth as YYYY-MM-DD strings, which sets the baseline at 3. The description adds nothing about the overlapping optional date parameters, leaving the agent to guess which one the API actually honors.

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?

The description names a domain (biorhythm) and an action (execute), so an agent can tell it computes a biorhythm chart. But "Execute biorhythm AstroChalit API" leans on vendor jargon and does not say what a biorhythm result contains or how it differs from the many astrology siblings such as get_compatibility_check or get_gemstone_suggestion.

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 pointer to an alternative tool. The only implied usage is that a birth date is involved, which comes from the schema rather than the description.

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