AstroLogics

Divisional chart (D2, D9, D10, D12)

get_divisional_chart

Read-onlyIdempotent

Get a divisional (varga) chart: D2 Hora, D9 Navamsa (marriage and dharma), D10 Dashamsa (career) or D12 Dwadashamsa (parents), with each graha's sign and house and the chart's interpretation where available. Uses a saved chart from the signed-in user's AstroLogics account or given birth details, with the chart features of the user's plan.

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": {
      "division": "<division>"
    },
    "name": "get_divisional_chart"
  }
}

Input Schema

Name	Required	Description
`date`	No	Birth date, YYYY-MM-DD (when not using a saved chart).
`time`	No	Local birth time, HH:MM (when not using a saved chart).
`chart`	No	A saved chart's id or name from list_my_charts. Or give the birth details below instead.
`division`	Yes	Which divisional chart.
`language`	No	Set to "hi" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi.
`latitude`	No	Birth latitude in decimal degrees (when not using a saved chart).
`longitude`	No	Birth longitude in decimal degrees (when not using a saved chart).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds entitlement context the annotations cannot convey: results depend on the signed-in user's saved charts and 'the chart features of the user's plan.' It also discloses conditional output with 'interpretation where available,' signaling that interpretation may be absent.

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?

Two sentences with no filler; the resource and its supported divisions are front-loaded, and the second sentence handles input sourcing and entitlement. Every clause carries information an agent needs.

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?

With no output schema, the description correctly describes the return shape (each graha's sign and house, plus interpretation where available) and covers the dual input path and plan gating. What is missing is failure guidance — e.g., behavior when birth details are partial or the division is unsupported by the user's plan.

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 baseline is 3. The description does add meaning beyond the schema for the division enum by attaching life-area semantics to D9/D10/D12, but it leaves D2 Hora unexplained and adds nothing about language or the coordinate fields beyond what the schema already documents.

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

Purpose4/5

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

States a specific verb and resource ('Get a divisional (varga) chart') and enumerates the exact supported divisions (D2 Hora, D9 Navamsa, D10 Dashamsa, D12 Dwadashamsa), matching the schema enum. It does not name or contrast with the sibling get_birth_chart (D1), so an agent must infer that the divisional charts live here rather than there.

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

Usage Guidelines3/5

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

The description gives useful selection context for the division parameter by tagging life areas (D9 marriage and dharma, D10 career, D12 parents) and explains the two input modes (saved chart vs. birth details). However, it never states when to prefer this over alternatives such as get_birth_chart or get_my_chart, nor what to do when neither a saved chart nor complete birth details are available.

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

All AstroLogics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?