Skip to main content
Glama
HellenicStar Astrology MCP Server

HellenicStar Astrology MCP Server

calculate_zodiacal_releasing

Read-onlyIdempotent

Compute Zodiacal Releasing periods from the Lot of Fortune and Lot of Spirit, returning level-1, level-2, and level-3 timelines with peak and loosing-of-the-bond markers.

Instructions

Zodiacal releasing (Valens, 360-day years) from the Lot of Fortune and Lot of Spirit. Returns all level-1 periods, the level-2 periods inside the level-1 period containing as_of, and the level-3 periods inside the current level-2 period, with peak and loosing-of-the-bond markers. as_of defaults to today. 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "calculate_zodiacal_releasing"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNo
foldNo
hourNo
yearNo
as_ofNo
monthNo
minuteNo
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: as_of, lots. Use these exact names.
location_idNo
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

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: as_of, lots. Use these exact names."
  2. Changed2 schema fields changed
    • 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 / 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."
  3. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds meaningful beyond-schema behavior: server checks run before results are returned, the mandatory verification round-trip, truncation marking in summary mode, and that verification references always identify the complete checked calculation. It stops short of describing error modes or pagination limits beyond the 'up to five rows' rule.

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

Conciseness3/5

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

Purpose and scope are front-loaded and most sentences carry real information. However, the detail_level/include sentences largely restate schema descriptions, and the closing sentence about verification references repeats an earlier point, adding length without new guidance.

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

Completeness3/5

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

With no output schema and 10 parameters, the description does a reasonable job of describing the returned structure (nested level-1/2/3 periods, markers, level-2/3 anchored to as_of). But the omission of any explanation for the datetime and location inputs leaves a real gap for correct invocation.

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

Parameters2/5

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

Schema coverage is only 20%, so the description must compensate, but it explains only as_of (defaults to today), include, and detail_level. The six datetime parameters (year, month, day, hour, minute, fold) and location_id are completely unaddressed — an agent cannot tell whether they are a birth datetime, a required set, or timezone-bearing.

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 technique (zodiacal releasing, Valens 360-day years), its sources (Lot of Fortune and Lot of Spirit), and exactly what is returned at each level with peak/loosing-of-the-bond markers. The level-1/2/3 scope implicitly separates it from the sibling calculate_zodiacal_releasing_l4, but it never names or contrasts that sibling explicitly.

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

Usage Guidelines4/5

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

Gives a clear conditional workflow: call verify_calculation_claims with the unchanged calculation_reference before interpreting, correct contradicted facts and reverify, and notes psychological interpretations are not checked. It also states when to use detail_level=summary versus omitting both for the full result. No guidance on when to prefer this over calculate_zodiacal_releasing_l4 or calculate_time_lords.

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