Skip to main content
Glama

AstroWay Hellenistic and traditional

Horary Planetary Hours

astroway_horary_planetary_hours
Read-onlyIdempotent

Return the planetary hour ruler at the exact moment of a horary question and check if it matches the ASC ruler.

[Group: Horary] [Endpoint: POST /v1/horary/planetary-hours] [Required: dayOfWeek, sunriseHour, sunsetHour] [Cost: 20 credits (Tier 2)]

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": {
      "dayOfWeek": "<dayOfWeek>",
      "sunriseHour": "<sunriseHour>",
      "sunsetHour": "<sunsetHour>"
    },
    "name": "astroway_horary_planetary_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
dayOfWeekYes
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
sunsetHourYes
currentHourNo
sunriseHourYes

Output Schema

NameRequiredDescriptionDefault
matchNo
hourEndNo
ascRulerNo
dayRulerNo
hourRulerNo
hourStartNo
hourNumberNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed22 schema fields changed
    • removedInput schema / properties / currentHour / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / currentHour / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / dayOfWeek / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / dayOfWeek / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / sunriseHour / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / sunriseHour / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / sunsetHour / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / sunsetHour / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / ascRuler / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / ascRuler / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / dayRuler / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / dayRuler / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / hourEnd / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / hourEnd / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / hourNumber / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / hourNumber / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / hourRuler / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / hourRuler / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / hourStart / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / hourStart / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / match / anyOf
      Removed value: -[
      -  {
      -    "type": "boolean"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / match / type
      Added value: +[
      +  "boolean",
      +  "null"
      +]
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational context the annotations cannot convey: the POST endpoint and the 20-credit Tier 2 cost, which matters for planning. It does not describe what the response contains, but an output schema exists so that is partially excused.

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 core sentence is front-loaded and waste-free, and the bracketed metadata block is compact. The block does mix routing-relevant info (required params) with billing info, but nothing is bloated.

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 6-parameter tool with three required, undocumented numeric parameters and no unit guidance, the description leaves the agent guessing how to construct a valid call. An output schema and annotations cover returns and safety, and cost is disclosed, but the input-format gap is the dominant risk and is unaddressed.

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%: dayOfWeek, sunriseHour, sunsetHour and currentHour have no descriptions at all. The description merely repeats which three are required and gives no units or format (fractional hours? 0-23? day index convention?), so it fails to compensate for the coverage gap. Only the fields/precision compact-mode parameters are documented, and that is in the schema, not the description.

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?

The description names a specific verb and resource: it returns the planetary hour ruler at the moment of a horary question and additionally checks the match against the ASC ruler. The horary/ASC-ruler framing distinguishes it from the plain calendar and streaming planetary-hour siblings, though it never names those siblings explicitly.

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?

Usage is implied by the horary framing (use it when judging a horary chart's hour agreement), but there is no explicit when-to-use or when-not clause, and no routing advice versus astroway_horary_horary, astroway_calendar_planetary_hours, or astroway_stream_planetary_hour_changes.

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