Skip to main content
Glama

One planet at any date

planet_position
Read-onlyIdempotent

One body's tropical position on a date, anywhere from 13,200 BC to AD 17,191, with its speed and whether it is retrograde. For historical and ancient dates; dates before 1582 are proleptic Gregorian.

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": {
      "body": "<body>",
      "date": "<date>"
    },
    "name": "planet_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
dateYes
time_utcNoHH:MM UTC (default 12:00)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, closed-world), and the description adds real domain behavior: the supported date span of 13,200 BC to AD 17,191, the tropical zodiac convention, the calendar convention before 1582, and the fact that speed and retrograde status come back. Precision/accuracy characteristics and the output format are not stated.

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

Conciseness5/5

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

Two tight sentences with the core capability front-loaded and the calendar caveat trailing where it belongs. No filler.

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

Completeness4/5

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

For a 3-parameter read-only computation with no output schema, the description states what is returned (position, speed, retrograde) and the valid date domain, which is what an agent needs to call it. Minor gaps remain around units/format of the returned position.

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

Parameters3/5

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

Schema description coverage is only 33% (only time_utc is documented), so the description must compensate. It partly does by implying the accepted date range, but it never explains the body enum (true_node, chiron) or the date string format beyond the era bound, leaving two of three parameters under-specified.

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?

Names a specific verb+resource: the tropical position of one body on a given date, plus the derived speed and retrograde flag. The 'one body' framing implicitly separates it from the multi-body siblings (sky_now, natal_chart), though no sibling is named 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?

'For historical and ancient dates' gives a clear usage context, and the proleptic Gregorian note tells the agent how to interpret pre-1582 inputs. There are no explicit exclusions or named alternatives, so it stops short of a 5.

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