Skip to main content
Glama
AstroChalit MCP Server

AstroChalit MCP Server

get_varshphal_saham

Calculate annual Saham points from birth date, time, and location for a chosen year to reveal sensitive placements in the Vedic annual horoscope.

Instructions

Execute varshphal_saham 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": {
      "day": "<day>",
      "month": "<month>",
      "year": "<year>",
      "hour": "<hour>",
      "minute": "<minute>",
      "second": "<second>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "yearInput": "<yearInput>"
    },
    "name": "get_varshphal_saham"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayYesDay of birth
hourYesHour of birth (0-23)
yearYesYear of birth (e.g., 1990)
monthYesMonth of birth (1-12)
minuteYesMinute of birth (0-59)
secondYesSecond of birth (0-59)
latitudeYesLatitude of birth place
timezoneNoTimezone of birth place (e.g. Asia/Kolkata). Defaults to Asia/Kolkata
longitudeYesLongitude of birth place
yearInputYesTarget year (e.g. 2025)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

D1.7/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 disclosure burden, and it discloses nothing: not the response shape, not whether the result is computed per target year, not whether a timezone default applies, not cost or rate behavior. For a 10-parameter compute endpoint this is a complete absence of 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.

Conciseness2/5

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

It is short, but brevity here is under-specification rather than economy: a single fragment naming an internal API. There is no front-loaded statement of purpose or return value to justify the sentence's place.

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

Completeness1/5

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

Ten parameters (nine required), no annotations, and no output schema mean the description must explain what the call produces and how birth details plus yearInput interact. It says none of that, leaving an agent unable to predict the response at all.

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 10 documented parameters, so the schema already explains day/month/year/hour/minute/second/latitude/longitude/timezone/yearInput. The description adds no additional meaning beyond that, which the high-coverage baseline permits, but it does nothing to explain how the birth data relates to the target yearInput.

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?

"Execute varshphal_saham AstroChalit API" restates the tool name plus a vendor label; the only verb is the generic "Execute." It never says what a "saham" is or what the tool returns, so an agent cannot distinguish it from siblings such as get_varshphal_details or get_varshphal_planets beyond the bare resource word.

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, when-not-to-use, or prerequisite guidance of any kind. Nothing tells the agent which of the many varshphal_* siblings this one should be preferred over, nor what condition makes this call appropriate.

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