Skip to main content
Glama

Calculate a chart from a place or coordinates

calculate_chart_from_known_place
Read-onlyIdempotent

SHOW THE BIRTH CHART. Use when the person wants to see their chart, planet positions, Navamsa, Dasamsa (D10) or another divisional chart, or running dasha. Pass varga (for example D10) to open on that divisional chart. Returns a compact readable summary (Lagna, planet table, current Vimshottari, birth Panchanga, Navamsa) and, in hosts that support MCP Apps, an interactive South Indian Rasi/Navamsa chart with a dasha timeline. For interpretation of a question use consult_jyotishya instead. Calculates a complete South Indian chart from a known catalogue place or explicit latitude, longitude, and IANA timezone supplied by the MCP host. Bare place names auto-resolve to the curated best-effort match with alternatives noted. This deterministic tool never invokes another AI model.

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": {
      "date": "<date>",
      "time": "<time>",
      "place": "<place>"
    },
    "name": "calculate_chart_from_known_place"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
nameNo
timeYes
focusNogeneral
placeYes
vargaNoDivisional chart to open on, for example D10 (Dasamsa, career) or D7 (Saptamsa, children). Every divisional chart is in the result either way.D1
languageNoen
latitudeNo
timezoneNo
longitudeNo
timezoneOffsetNo
birthTimeAccuracyMinutesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / varga
      Added value: +{
      +  "default": "D1",
      +  "description": "Divisional chart to open on, for example D10 (Dasamsa, career) or D7 (Saptamsa, children). Every divisional chart is in the result either way.",
      +  "enum": [
      +    "D1",
      +    "D2",
      +    "D3",
      +    "D4",
      +    "D5",
      +    "D6",
      +    "D7",
      +    "D8",
      +    "D9",
      +    "D10",
      +    "D12",
      +    "D16",
      +    "D20",
      +    "D24",
      +    "D27",
      +    "D30",
      +    "D40",
      +    "D45",
      +    "D60",
      +    "D81",
      +    "D108",
      +    "D144"
      +  ],
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "date",
      -  "time",
      -  "place"
      -]New value: +[
      +  "date",
      +  "time",
      +  "place"
      +]
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the bar is lower; the description still adds real behavior: a compact readable summary plus an interactive chart only on MCP Apps hosts, and that bare place names auto-resolve to a curated best-effort match with alternatives noted. It also states the tool is deterministic and never invokes another model, which is valuable trust context; it says nothing about error behavior for unresolvable places.

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

Conciseness5/5

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

Front-loaded with the core action, then trigger conditions, then the key parameter hint, then return shape, then the alternative and caveats. Sentences are dense but each carries distinct information, with only mild restatement of the 'South Indian chart' framing.

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

Completeness4/5

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

An output schema exists, yet the description still usefully summarizes what comes back and flags host-dependent interactive rendering, which an agent needs to set expectations. The remaining gap is semantic coverage of the non-required parameters (focus, language, birthTimeAccuracyMinutes) and precedence between place and coordinates.

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?

With 12 parameters and only 8% schema description coverage, the description must carry weight; it explains varga (example D10, and that all divisional charts are returned regardless) and clarifies that place may be a catalogue name or supplemented by explicit latitude, longitude and IANA timezone. Date, time, timezoneOffset, birthTimeAccuracyMinutes, focus, language and name remain unexplained, and it never says how place and coordinate parameters interact when both are supplied.

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

Purpose5/5

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

The description opens with a specific verb and resource ('SHOW THE BIRTH CHART') and immediately lists the concrete outputs (Lagna, planet table, Vimshottari, Panchanga, Navamsa), which lets an agent separate it from the interpretation sibling consult_jyotishya.

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

Usage Guidelines4/5

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

It gives an explicit trigger ('Use when the person wants to see their chart, planet positions... or running dasha') and names an alternative for a different intent ('For interpretation of a question use consult_jyotishya instead'). It does not address when to prefer the other chart-calculation siblings, so the routing picture is clear but not complete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources