Skip to main content
Glama

Asterwise

by com.asterwise.mcp

Divisional Chart

asterwise_get_divisional_chart
Read-onlyIdempotent

Computes divisional (varga) chart positions from BirthData; pass chart_type for one varga, or omit chart_type for all sixteen.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — anchor D1 before reading higher vargas. AFTER: None.

INPUT CONTRACT: chart_type enum is enforced locally (Pydantic). BirthData follows the global contract.

DO NOT CONFUSE WITH: asterwise_get_natal_chart — radix chart with houses and drishti, not the full varga dictionary. asterwise_get_chart_strength — embeds vargas inside strength metrics, different primary payload.

Full output and error contract: https://docs.asterwise.com/mcp/tools/get-divisional-chart/

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birthYesBirth data for a single person.
chart_typeNoDivisional chart to return, D1 to D60. Omit to return all 16 charts.
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / properties / chart_type / description
      Added value: +"Divisional chart to return, D1 to D60. Omit to return all 16 charts."
    • addedInput schema / properties / response_format / description
      Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."
  2. Changed8 schema fields changed
    • changedInput schema / properties / birth / properties / date / description
      Previous value: -"Birth date in YYYY-MM-DD format. Example: '1985-11-12'"New value: +"Birth date YYYY-MM-DD."
    • changedInput schema / properties / birth / properties / lat / description
      Previous value: -"Birth latitude in decimal degrees. North positive, south negative. Example: 19.0760 for Mumbai, -33.8688 for Sydney"New value: +"Latitude in decimal degrees, north positive (Mumbai 19.076)."
    • changedInput schema / properties / birth / properties / lon / description
      Previous value: -"Birth longitude in decimal degrees. East positive, west negative. Example: 72.8777 for Mumbai, -74.0060 for New York"New value: +"Longitude in decimal degrees, east positive (Mumbai 72.8777)."
    • changedInput schema / properties / birth / properties / person_name / description
      Previous value: -"Name of the person for this chart. Example: 'Arjun Mehta'"New value: +"Person's name, used in labels only."
    • changedInput schema / properties / birth / properties / time / description
      Previous value: -"Birth time in HH:MM 24-hour format. Example: '06:45'. Omit entirely if the birth time is unknown: a sunrise chart is used and birth_time_provided returns false. Do not pass '00:00' for an unknown time, it is treated as a real midnight birth and returns a confidently wrong ascendant."New value: +"Birth time HH:MM (24h), e.g. '06:45'. Omit if unknown (a sunrise chart is used and birth_time_provided=false); never pass '00:00' for unknown."
    • changedInput schema / properties / birth / properties / timezone / description
      Previous value: -"IANA timezone for the birth location. Examples: 'Asia/Kolkata' (India), 'America/New_York' (New York), 'Europe/London' (London), 'Asia/Tokyo' (Japan), 'America/Los_Angeles' (Los Angeles), 'Europe/Paris' (Paris), 'Asia/Dubai' (Dubai), 'Asia/Singapore' (Singapore), 'America/Chicago' (Chicago), 'Australia/Sydney' (Sydney). Default: Asia/Kolkata"New value: +"IANA timezone of the birth place, e.g. 'Asia/Kolkata', 'America/New_York', 'Europe/London'. Default: Asia/Kolkata"
    • addedInput schema / properties / response_format / default
      Added value: +"markdown"
    • changedInput schema / required
      Previous value: -[
-  "birth",
-  "response_format"
-]New value: +[
+  "birth"
+]
  3. Changed6 schema fields changed
    • addedInput schema / properties / birth / properties / time / anyOf
      Added value: +[
+  {
+    "pattern": "^\\d{2}:\\d{2}$",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / birth / properties / time / default
      Added value: +null
    • changedInput schema / properties / birth / properties / time / description
      Previous value: -"Birth time in HH:MM format (24-hour). Example: '06:45'. Use '00:00' if unknown."New value: +"Birth time in HH:MM 24-hour format. Example: '06:45'. Omit entirely if the birth time is unknown: a sunrise chart is used and birth_time_provided returns false. Do not pass '00:00' for an unknown time, it is treated as a real midnight birth and returns a confidently wrong ascendant."
    • removedInput schema / properties / birth / properties / time / pattern
      Removed value: -"^\\d{2}:\\d{2}$"
    • removedInput schema / properties / birth / properties / time / type
      Removed value: -"string"
    • changedInput schema / properties / birth / required
      Previous value: -[
-  "date",
-  "time",
-  "lat",
-  "lon"
-]New value: +[
+  "date",
+  "lat",
+  "lon"
+]
  4. Changed5 schema fields changed
    • addedInput schema / properties / chart_type / anyOf
      Added value: +[
+  {
+    "enum": [
+      "D1",
+      "D2",
+      "D3",
+      "D4",
+      "D7",
+      "D9",
+      "D10",
+      "D12",
+      "D16",
+      "D20",
+      "D24",
+      "D27",
+      "D30",
+      "D40",
+      "D45",
+      "D60"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / chart_type / default
      Added value: +null
    • removedInput schema / properties / chart_type / enum
      Removed value: -[
-  "D1",
-  "D2",
-  "D3",
-  "D4",
-  "D7",
-  "D9",
-  "D10",
-  "D12",
-  "D16",
-  "D20",
-  "D24",
-  "D27",
-  "D30",
-  "D40",
-  "D45",
-  "D60"
-]
    • removedInput schema / properties / chart_type / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
-  "birth",
-  "chart_type",
-  "response_format"
-]New value: +[
+  "birth",
+  "response_format"
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the bar is lower. The description adds useful behavioral context: the default returns all sixteen vargas, chart_type selection overrides that, and there is a recommended D1 anchoring workflow. It stops short of detailing error behavior, but the linked full contract covers that, and the output schema exists.

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

Conciseness4/5

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

The description is well-structured with a front-loaded summary followed by WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH, and a documentation link. Every section earns its place, though the INPUT CONTRACT sentence about local Pydantic enforcement is slightly redundant with schema information and could be trimmed without losing value.

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?

The description covers the core purpose, the selection behavior, workflow prerequisites, sibling distinctions, and points to a full output/error contract. With an output schema present and a documentation link, an agent has enough to call the tool correctly. It doesn't describe return structure inline, but that gap is adequately covered by the output schema and linked docs.

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 already documents all parameters thoroughly. The description's chart_type notes ('pass chart_type for one varga, or omit for all sixteen') largely mirror the schema description and add little new semantic value. It does minimally reinforce the selection behavior, so the baseline 3 is appropriate.

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 uses a specific verb ('Computes') and resource ('divisional (varga) chart positions from BirthData'), immediately clarifies the single-chart vs all-sixteen behavior, and explicitly distinguishes the tool from sibling tools. An agent can tell this apart from asterwise_get_natal_chart and asterwise_get_chart_strength without opening schemas.

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

Usage Guidelines5/5

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

The description provides a clear workflow hint (BEFORE: asterwise_get_natal_chart to anchor D1) and a dedicated 'DO NOT CONFUSE WITH' section naming two siblings with precise differentiators (radix chart vs full varga dictionary; strength metrics vs primary payload). This is explicit when-to-use and when-not-to-use guidance.

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

All Asterwise toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Many tools are well-differentiated by explicit 'DO NOT CONFUSE WITH' notes, but the sheer number of near-neighbor pairs (e.g., crystal vs gemstone recommendations, natal chart variants, dasha systems, compatibility systems, tarot draw variants) creates real selection risk. The descriptions mitigate overlap, but an agent browsing 103 tools will struggle to pick the right one.

Naming Consistency5/5

Every tool follows the asterwise_get_* or asterwise_draw_* prefix convention with a clear noun phrase (e.g., asterwise_get_natal_chart, asterwise_draw_tarot_cards). The two verbs 'get' and 'draw' are semantically appropriate, and there are no camelCase or mixed-style names.

Tool Count1/5

103 tools is far beyond a manageable MCP surface. While the domain is broad (Vedic astrology, Western astrology, numerology, tarot, crystals, dream symbols), the server bundles multiple distinct domains into one namespace, making it nearly impossible for an agent to discover the right tool efficiently.

Completeness4/5

The surface is impressively comprehensive across astrology, numerology, tarot, and remedies, with deep coverage of dasha systems, compatibility frameworks, and chart types. Minor gaps exist (e.g., no tarot interpretation endpoint, no batch operations, no update/delete since it's read-only data), but for a reference/prediction API the coverage is strong.

Resources