Skip to main content
Glama
astroway

astroway-mcp

Official
by astroway

Lots of Seven

astroway_hellenistic_hand_lots_of_seven
Read-onlyIdempotent

Calculate seven primary Hellenistic Lots of the Hand tradition from date, time, latitude, and longitude for chart interpretation.

Instructions

Seven primary Lots per Hand.

[Group: Hellenistic: Hand tradition] [Endpoint: POST /v1/hellenistic/hand/lots-of-seven] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
ayanamsaNoSidereal school by name. Lahiri when omitted. Equivalent to ayanamsaId; send either.
latitudeYes
timezoneNoIANA zone name such as Europe/Kyiv, or auto to look the zone up from latitude and longitude. The server takes the offset that zone kept at this local date and time, summer time included, and uses it in place of timezoneOffset. A clock time that happened twice takes the first occurrence; one skipped when clocks went forward takes the offset from before the change. Abbreviations such as EST are refused. Before 1970 the tz database is not reliable for every place, so send timezoneOffset when the local clock is known.
cosmogramNo
longitudeYes
ayanamsaIdNo
zodiacTypeNo
houseSystemNoP
timezoneOffsetNoHours from UTC at the given moment, not minutes. Fractional zones are hours too: 5.5 for India, 5.75 for Nepal, -3.5 for Newfoundland. Defaults to 0, meaning UTC. Ignored when timezone is sent.

Output Schema

NameRequiredDescriptionDefault
sectNo
sourceNo
doctrineNo
disclaimerNo
lotsOfSevenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world behavior. The description adds useful operational context: endpoint, credit cost, and required inputs, but does not cover auth, rate limits, or response 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?

The description is very short and front-loads the core phrase before bracketed metadata. It is concise, though the metadata lines are fragmentary rather than explanatory.

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

Completeness2/5

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

For a 13-parameter specialized calculation tool with low schema description coverage, this is too terse. It omits what the seven Lots are, how optional astrological settings affect results, and when the tool is appropriate.

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 description coverage is only 23%, and the description merely repeats the four required fields already marked required in the schema. It says nothing about the nine optional parameters, including major astrological settings like houseSystem, zodiacType, ayanamsa, and cosmogram.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource, "Seven primary Lots per Hand," but gives no verb and does not explain what a "Lot" calculation returns. It is distinguishable from generic tools but not clearly from Hellenistic siblings such as the Lots of 15 tool.

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

Usage Guidelines2/5

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

No when-to-use guidance is provided, no exclusions, and no sibling alternatives are named. The nearest related Hellenistic Lot tools exist in the sibling list, but the description does not route the agent between them.

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

Deploy Server

Other Tools