Skip to main content
Glama
HellenicStar Astrology MCP Server

HellenicStar Astrology MCP Server

calculate_natal_salience

Read-onlyIdempotent

Extracts rule-based natal priorities and candidate focus groups from exact birth date/time and a confirmed location, returning source evidence and explicit partial availability.

Instructions

Extract rule-based natal priorities when the user needs candidate focus groups with source evidence. Use calculate_natal_structure_graph for the complete unselected relationship graph, or calculate_natal_chart for positions and houses. Requires exact local birth date/time and a confirmed location_id. Returns focus_selection, all ten planet_profiles, relationship_views separating dignity dependencies from direct aspects, state evidence, reading groups and source_graph; jones_view and view_comparison retain Jones as a separate perspective that does not select natal priorities. Missing house/axis layers remain explicit as partial availability. Broad selections are allowed: no global importance score, forced single core, psychological inference or remedy verdict. Reception criteria and bounded aspect dynamics describe calculated conditions, not efficacy or unlimited perfection. Scope, rulers and orbs are explained in the input fields. Detailed selection rules and version history: docs/natal-salience.md. Server checks run before successful results are returned. Before interpreting this data, call verify_calculation_claims with its unchanged calculation_reference and draft source-field claims. Correct contradicted facts and reverify before the final answer. Psychological interpretations are not checked. Optional detail_level=summary previews object/nested rows (up to five), preserves complete scalar membership lists, and marks truncation; include selects top-level content fields. Omit both for the original full result. Verification references always identify the complete checked calculation.

Input Schema

NameRequiredDescriptionDefault
dayNoLocal civil birth day; must form a valid date with year and month.
foldNoFor an ambiguous repeated local time, use 0 for the earlier occurrence or 1 for the later one after user confirmation. Otherwise omit.
hourNoExact local civil birth hour, 0-23; not UTC. Do not substitute an unknown time.
yearNoExact birth year in the local civil calendar. Birth fields are required for a successful calculation; ask for missing data rather than guessing.
monthNoLocal civil birth month, 1-12; interpreted with year and day.
scopeNoStatistical origins: classical7 uses Sun through Saturn; ten adds Uranus, Neptune and Pluto. Does not remove the ten complete profiles or restrict which planets chains may traverse.classical7
minuteNoExact local civil birth minute, 0-59.
includeNoOptional 1-30 top-level content field names, each 1-80 characters. Omit to return all content. Control/provenance fields remain; unknown or control field names return invalid_input with available_fields. Known selectable fields: aspect_dynamics, attention_layers, availability, candidate_planets, core_structures, evidence_index, evidence_matrix, focus_selection, global_distribution, house_ruler_links, interpretations, jones_view, method, planet_condition_assessments, planet_profiles, policy_comparison, priority_aspects, priority_configurations, priority_decisions, priority_planets, reading_plan, reception_facts, relationship_views, resource_checks, resource_decisions, schema_version, selection_audit, source_graph, supplementary_contacts, view_comparison. Use these exact names.
axis_orbNoMaximum axis-contact orb in degrees, finite 0-10; ASC/MC use actual chart axes, with opposite-axis expressions merged.
orb_viewNoUniform inclusive major-aspect orb in degrees: 6 (default), 8 or 10. Applies to all five major aspects and ten planets.
rulershipNoDispositor edge convention, traditional or modern; separate from the number of statistical origins.traditional
tight_orbNoTight-aspect candidate threshold in degrees, finite 0-10 and no greater than orb_view. Does not discard other selected-view aspects.
location_idNoCopy a confirmed ID from resolve_birth_coordinates or search_birthplace. It supplies coordinates and the IANA timezone; a person name does not replace it.
detail_levelNofull returns complete calculation content. summary previews up to five object/nested rows per list, preserves scalar membership lists, and reports omitted counts. References still identify the full calculation.full
dynamics_daysNoBounded forward search horizon in days, integer 1-90. Searches the current aspect branch for its first exact contact and reports intervening stations/ingresses; no match means none found in this horizon.
include_mc_rulerNoInclude the MC sign ruler in identity candidates when MC is available; false keeps the default identity selection.
reception_policyNoChoose dignity alone; dignity plus sign geometry; dignity plus a selected degree aspect; or dignity plus a selected degree aspect and applying status. These are distinct criteria, not efficacy judgments.dignity_only
distribution_pointsNoPoints for element/modality distribution: ten planets, or ten plus available ASC and MC. Does not change ten-planet aspect motifs.ten_plus_asc_mc

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • changedInput schema / properties / include / description
      Previous value: -"Optional 1-30 top-level content field names, each 1-80 characters. Omit to return all content. Control/provenance fields remain; unknown or control field names return invalid_input with available_fields."New value: +"Optional 1-30 top-level content field names, each 1-80 characters. Omit to return all content. Control/provenance fields remain; unknown or control field names return invalid_input with available_fields. Known selectable fields: aspect_dynamics, attention_layers, availability, candidate_planets, core_structures, evidence_index, evidence_matrix, focus_selection, global_distribution, house_ruler_links, interpretations, jones_view, method, planet_condition_assessments, planet_profiles, policy_comparison, priority_aspects, priority_configurations, priority_decisions, priority_planets, reading_plan, reception_facts, relationship_views, resource_checks, resource_decisions, schema_version, selection_audit, source_graph, supplementary_contacts, view_comparison. Use these exact names."
  2. Changed18 schema fields changed
    • addedInput schema / properties / axis_orb / description
      Added value: +"Maximum axis-contact orb in degrees, finite 0-10; ASC/MC use actual chart axes, with opposite-axis expressions merged."
    • addedInput schema / properties / day / description
      Added value: +"Local civil birth day; must form a valid date with year and month."
    • addedInput schema / properties / detail_level / description
      Added value: +"full returns complete calculation content. summary previews up to five object/nested rows per list, preserves scalar membership lists, and reports omitted counts. References still identify the full calculation."
    • addedInput schema / properties / distribution_points / description
      Added value: +"Points for element/modality distribution: ten planets, or ten plus available ASC and MC. Does not change ten-planet aspect motifs."
    • addedInput schema / properties / dynamics_days / description
      Added value: +"Bounded forward search horizon in days, integer 1-90. Searches the current aspect branch for its first exact contact and reports intervening stations/ingresses; no match means none found in this horizon."
    • addedInput schema / properties / fold / description
      Added value: +"For an ambiguous repeated local time, use 0 for the earlier occurrence or 1 for the later one after user confirmation. Otherwise omit."
    • addedInput schema / properties / hour / description
      Added value: +"Exact local civil birth hour, 0-23; not UTC. Do not substitute an unknown time."
    • addedInput schema / properties / include / description
      Added value: +"Optional 1-30 top-level content field names, each 1-80 characters. Omit to return all content. Control/provenance fields remain; unknown or control field names return invalid_input with available_fields."
    • addedInput schema / properties / include_mc_ruler / description
      Added value: +"Include the MC sign ruler in identity candidates when MC is available; false keeps the default identity selection."
    • addedInput schema / properties / location_id / description
      Added value: +"Copy a confirmed ID from resolve_birth_coordinates or search_birthplace. It supplies coordinates and the IANA timezone; a person name does not replace it."
    • addedInput schema / properties / minute / description
      Added value: +"Exact local civil birth minute, 0-59."
    • addedInput schema / properties / month / description
      Added value: +"Local civil birth month, 1-12; interpreted with year and day."
    • addedInput schema / properties / orb_view / description
      Added value: +"Uniform inclusive major-aspect orb in degrees: 6 (default), 8 or 10. Applies to all five major aspects and ten planets."
    • addedInput schema / properties / reception_policy / description
      Added value: +"Choose dignity alone; dignity plus sign geometry; dignity plus a selected degree aspect; or dignity plus a selected degree aspect and applying status. These are distinct criteria, not efficacy judgments."
    • addedInput schema / properties / rulership / description
      Added value: +"Dispositor edge convention, traditional or modern; separate from the number of statistical origins."
    • addedInput schema / properties / scope / description
      Added value: +"Statistical origins: classical7 uses Sun through Saturn; ten adds Uranus, Neptune and Pluto. Does not remove the ten complete profiles or restrict which planets chains may traverse."
    • addedInput schema / properties / tight_orb / description
      Added value: +"Tight-aspect candidate threshold in degrees, finite 0-10 and no greater than orb_view. Does not discard other selected-view aspects."
    • addedInput schema / properties / year / description
      Added value: +"Exact birth year in the local civil calendar. Birth fields are required for a successful calculation; ask for missing data rather than guessing."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so safety is covered. The description still adds real value beyond them: it discloses what the result does NOT contain (no global importance score, forced single core, psychological inference or remedy verdict), that partial availability is possible when house/axis layers are missing, and that server checks run before results return. It does not, however, describe rate limits, auth, or pagination behavior.

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 with purpose and sibling routing, and nearly every sentence carries operational meaning (scope distinctions, broad-selection allowances, verification loop). It is dense and long, with several tightly packed caveat clauses that could be trimmed, but nothing is purely redundant.

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?

Despite no output schema, the description enumerates the returned fields (focus_selection, ten planet_profiles, relationship_views, state evidence, reading groups, source_graph, jones_view, view_comparison) and explains jones_view/view_comparison as a non-selecting perspective. For an 18-parameter analytical tool it gives an agent everything needed to call and interpret it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema carries most parameter meaning and baseline is 3. The description adds top-level semantics the schema alone does not: it explains detail_level=summary row-truncation behavior and that verification references always identify the complete calculation, and points the reader to input fields for scope/rulers/orbs interpretation.

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 (extract) and resource (rule-based natal priorities / candidate focus groups) with source evidence. Explicitly distinguishes itself from calculate_natal_structure_graph ('complete unselected relationship graph') and calculate_natal_chart ('positions and houses'), so an agent can route correctly 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?

Names the alternatives and the conditions that select them, states the prerequisites (exact local birth date/time, confirmed location_id from resolve_birth_coordinates/search_birthplace), and prescribes a downstream call to verify_calculation_claims before interpreting. Both when-to-use and when-not are covered.

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