Skip to main content
Glama

Char Dasha

asterwise_get_char_dasha
Read-onlyIdempotent

Computes Char Dasha from birth data and returns sign lords as period rulers with ISO-dated Maha and Antar sequences plus karaka mappings.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises the chart before interpreting sign-based lords. AFTER: asterwise_get_dasha — optional Vimshottari cross-check for the same native.

INPUT CONTRACT: cycles (optional int 1–3, default 1): every further cycle repeats the first cycle's signs, order and years (K.N. Rao). Period start_date and end_date in data.periods[] are YYYY-MM-DD (ISO), unlike asterwise_get_dasha which uses DD/MM/YYYY in its tree. All other parameters follow the BirthData global contract.

DO NOT CONFUSE WITH: asterwise_get_dasha — Vimshottari planet lords with DD/MM/YYYY in periods[], not sign-based Char Dasha. asterwise_get_yogini_dasha — eight Yoginis and data.periods.root[], not classical signs.

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

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": {
      "birth": "<birth>"
    },
    "name": "asterwise_get_char_dasha"
  }
}

Input Schema

NameRequiredDescriptionDefault
birthYesBirth data for tools that need the exact birth time (no sunrise fallback).
cyclesNoChar Dasha cycles to return, 1-3 (default 1). Every further cycle repeats the first cycle's signs, order and years (K.N. Rao).
response_formatNoOutput format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload.markdown

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cycles / description
      Previous value: -"Char Dasha cycles to return, 1-3 (default 1). Cycle 2 runs the same signs for 12 minus their first-cycle years; cycle 3 repeats cycle 1 (K.N. Rao)."New value: +"Char Dasha cycles to return, 1-3 (default 1). Every further cycle repeats the first cycle's signs, order and years (K.N. Rao)."
  2. Changed1 schema field changed
    • addedInput schema / properties / cycles
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Char Dasha cycles to return, 1-3 (default 1). Cycle 2 runs the same signs for 12 minus their first-cycle years; cycle 3 repeats cycle 1 (K.N. Rao)."
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / birth / description
      Previous value: -"Birth data for tools that need the exact birth time.\n\nTheir API endpoints have no sunrise fallback and reject a request without\na time, so the time is required here instead of failing upstream."New value: +"Birth data for tools that need the exact birth time (no sunrise fallback)."
  4. Changed7 schema fields changed
    • changedInput schema / properties / birth / description
      Previous value: -"Birth data for a single person."New value: +"Birth data for tools that need the exact birth time.\n\nTheir API endpoints have no sunrise fallback and reject a request without\na time, so the time is required here instead of failing upstream."
    • removedInput schema / properties / birth / properties / time / anyOf
      Removed value: -[
      -  {
      -    "pattern": "^\\d{2}:\\d{2}$",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / birth / properties / time / default
      Removed value: -null
    • changedInput schema / properties / birth / properties / time / description
      Previous 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."New value: +"Birth time HH:MM (24h), e.g. '06:45'. Required: this tool has no sunrise fallback. If the user doesn't know it, say so rather than guessing; never pass '00:00' for unknown."
    • addedInput schema / properties / birth / properties / time / pattern
      Added value: +"^\\d{2}:\\d{2}$"
    • addedInput schema / properties / birth / properties / time / type
      Added value: +"string"
    • changedInput schema / properties / birth / required
      Previous value: -[
      -  "date",
      -  "lat",
      -  "lon"
      -]New value: +[
      +  "date",
      +  "time",
      +  "lat",
      +  "lon"
      +]
  5. Changed1 schema field changed
    • addedInput schema / properties / response_format / description
      Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."
  6. 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"
      +]
  7. 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"
      +]
  8. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behaviour, so the safety profile is covered. The description adds value beyond that: it warns that the birth time is mandatory with no sunrise fallback, documents the ISO date convention that differs from the sibling tool, and explains cycle repetition. It does not discuss cost, rate limits, or failure modes beyond the docs link.

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?

Front-loaded one-sentence summary, then clearly labelled WORKFLOW, INPUT CONTRACT and DO NOT CONFUSE WITH sections, so a skimming agent still gets the routing information. Slightly padded by restating the cycles semantics already present in the schema, which keeps it from a 5.

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

Completeness5/5

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

For a single-purpose computation tool with a full output schema, the description covers everything the agent needs: inputs, output shape, temporal format, prerequisite tools, disambiguation from siblings, and a link to the full output/error contract. Nothing required to invoke it correctly is missing.

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% and the cycles parameter's schema text already contains the K.N. Rao repetition rule, so the description largely repeats rather than extends it. The one genuinely additive note is the ISO vs DD/MM/YYYY contrast with get_dasha, which is output-contract rather than parameter guidance. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb (computes), a specific resource (Char Dasha from birth data), and names the exact output artefacts (sign lords as period rulers, ISO-dated Maha/Antar sequences, karaka mappings). It explicitly differentiates itself from the two nearest siblings, get_dasha and get_yogini_dasha, by naming their rulers and period formats.

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?

Provides an explicit BEFORE/AFTER workflow (natal chart first, Vimshottari cross-check after) plus a DO NOT CONFUSE WITH block naming two alternatives and the distinguishing features of each. An agent has no inference left to do about when to pick this tool.

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