Skip to main content
Glama

AstroWay Hellenistic and traditional

Temple Doctrine

astroway_helg_temple_doctrine
Read-onlyIdempotent

Temple-house assignments per Greenbaum.

[Group: Hellenistic: Greenbaum tradition] [Endpoint: POST /v1/hellenistic/greenbaum/temple-doctrine] [Required: date, time, latitude, longitude] [Cost: 10 credits (Tier 1)]

(Cursor-friendly alias for astroway_hellenistic_greenbaum_temple_doctrine.)

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": {
      "date": "<date>",
      "time": "<time>",
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_helg_temple_doctrine"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
dateYes
nameNo
timeYes
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
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
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
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
sourceNo
templesNo
doctrineNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / ayanamsaId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / ayanamsaId / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / disclaimer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / disclaimer / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / doctrine / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / doctrine / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / source / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / source / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / temples / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "cuspRuler": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "cuspSign": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "house": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "occupants": {
      -              "anyOf": [
      -                {
      -                  "items": {
      -                    "anyOf": [
      -                      {},
      -                      {
      -                        "type": "null"
      -                      }
      -                    ]
      -                  },
      -                  "type": "array"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "templeName": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "topos": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "cuspRuler": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "cuspSign": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "house": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "occupants": {
      +              "anyOf": [
      +                {
      +                  "items": {
      +                    "anyOf": [
      +                      {},
      +                      {
      +                        "type": "null"
      +                      }
      +                    ]
      +                  },
      +                  "type": "array"
      +                },
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            },
      +            "templeName": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "topos": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds genuinely new behavioral facts the annotations do not: the endpoint path, the four required inputs, and a 10-credit Tier 1 cost, which matters for budget-aware agents. It does not address the apparent tension between a POST endpoint and readOnlyHint, nor whether results are cached, so it is strong but not complete.

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 purpose is front-loaded in the first line and the bracketed metadata (group, endpoint, required, cost) is scannable rather than prose. There is no filler or repetition, though the tag-block format spends several lines on metadata that could be folded more tightly.

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?

For a 15-parameter, mathematically involved chart calculation, the description covers cost, endpoint, required inputs, and the alias relationship, and an output schema exists so return values need not be explained. However, it never indicates what kind of result (houses, lots, sect-based assignments) comes back or which optional parameters change the computation, leaving meaningful gaps for a tool of this complexity.

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 33% across 15 parameters, so the description needs to compensate and does not. It restates the four required fields (date, time, latitude, longitude) that the schema already marks as required, and says nothing about the undocumented parameters such as zodiacType, houseSystem, cosmogram, city, or name, nor about which defaults matter for this Greenbaum technique.

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?

"Temple-house assignments per Greenbaum" names a specific technique and the tradition it belongs to, which distinguishes it from the Brennan, Hand, and Schmidt Hellenistic siblings in the list. The parenthetical alias note also explains its relationship to astroway_hellenistic_greenbaum_temple_doctrine. It falls short of 5 because "temple-house assignments" is jargon an agent may not be able to interpret without domain knowledge of what the output actually contains.

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

Usage Guidelines3/5

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

The description gives no when-to-use or when-not-to-use guidance relative to the many other Hellenistic techniques offered. The only selection aid is the note that this is a "cursor-friendly alias" of the canonical Greenbaum temple-doctrine tool, which implies it is interchangeable and preferred in cursor/pagination contexts. That is a useful but narrow usage hint rather than real routing guidance.

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