Skip to main content
Glama

KP Significators

asterwise_get_kp_significators
Read-onlyIdempotent

Computes KP significator chains for all houses or one optional house from BirthData and returns house tables plus planet-tier reverse indexes.

WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_kp_chart — establish cusps before significators. AFTER: None.

INPUT CONTRACT: house_number optional int 1..12; omit for all twelve.

DO NOT CONFUSE WITH: asterwise_get_kp_chart — cusps and sub-lords, not tiered significator unions. asterwise_get_natal_chart — classical drishti matrices differ from KP significator tiers.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birthYesBirth data for tools that need the exact birth time (no sunrise fallback).
house_numberNoHouse number 1-12. Omit to cover all twelve houses.
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.

  1. 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)."
  2. 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"
      +]
  3. Changed2 schema fields changed
    • addedInput schema / properties / house_number / description
      Added value: +"House number 1-12. Omit to cover all twelve houses."
    • addedInput schema / properties / response_format / description
      Added value: +"Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload."
  4. 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"
      +]
  5. 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"
      +]
  6. 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 and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: an ordering dependency on asterwise_get_kp_chart, the fact that the tool reads BirthData with no sunrise fallback, and the shape of the result (house tables plus planet-tier reverse indexes). It does not discuss cost, rate limits, or failure modes, which is acceptable given the annotations and output schema.

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 one-line summary is front-loaded and the labeled sections (WORKFLOW, INPUT CONTRACT, DO NOT CONFUSE WITH) make the routing information scannable rather than buried in prose. It is slightly padded by the redundant INPUT CONTRACT line and the external docs URL, but nothing is materially wasteful.

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 a full input schema, a rich nested birth object, an output schema, and safety annotations, the description covers the remaining gaps an agent needs: when to run it relative to the KP chart tool, and which sibling tools it is not. The only omission is domain context on what a 'significator tier' means, which is reasonable to defer to the linked documentation.

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 every parameter (birth fields, ayanamsa, timezone, house_number, response_format) is documented in the schema itself, including the important 'never pass 00:00 for unknown' warning. The description's INPUT CONTRACT ('house_number optional int 1..12; omit for all twelve') only restates what the schema already says, so baseline 3 applies.

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 first sentence states a specific verb and resource ('Computes KP significator chains') and names the scope ('all houses or one optional house from BirthData'), plus what it returns ('house tables plus planet-tier reverse indexes'). The DO NOT CONFUSE WITH section explicitly separates it from asterwise_get_kp_chart and asterwise_get_natal_chart, so an agent can identify it without opening any schema.

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 WORKFLOW block gives an explicit precondition ('BEFORE: RECOMMENDED — asterwise_get_kp_chart — establish cusps before significators') and states there is no follow-up tool. The DO NOT CONFUSE WITH section names two alternatives and explains the discriminating dimension (cusps/sub-lords vs. tiered significator unions; drishti matrices vs. KP tiers).

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