Skip to main content
Glama

Solar or lunar return

returns
Read-onlyIdempotent

The solar return for a year (the moment the Sun returns to its birth position, the chart for that year) or the most recent lunar return (the last time the Moon reached its birth position), cast for the birthplace or another location.

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>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "timezone": "<timezone>",
      "kind": "<kind>"
    },
    "name": "returns"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD
kindYes
timeNoLocal clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable.
yearNoSolar return year (default this year)
placeNoBirthplace name, echoed back so the user can check the coordinates
latitudeYesBirthplace latitude in decimal degrees (north positive)
timezoneYesIANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it.
longitudeYesBirthplace longitude in decimal degrees (east positive)
return_latitudeNoWhere the person is for the return, if not the birthplace
return_longitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world behavior, so the safety profile is covered. The description usefully adds that the lunar variant returns the most recent occurrence rather than a requested year, and that the chart can be relocated. It says nothing about response shape, precision, or the noon fallback when time is omitted.

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?

A single front-loaded sentence with two clarifying parentheticals; nothing is wasted and the distinction between the two modes arrives before the location caveat. Slightly dense, but each clause carries information.

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 10-parameter tool with no output schema, the description covers both modes and the relocation option, but leaves the caller to infer the result contents and the significance of omitting time. Adequate, with a modest gap in what the returned chart actually contains.

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

Parameters4/5

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

Schema coverage is 80%, so the baseline is 3, but the description genuinely adds meaning: it clarifies that the year parameter applies only to the solar variant and that lunar is 'most recent', and 'cast for the birthplace or another location' explains the intent of the return_latitude/return_longitude pair, which the schema leaves partly undescribed.

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 concrete operation on a concrete artifact — the solar return chart for a year and the most recent lunar return — and defines each in plain terms (Sun returning to birth position, Moon reaching birth position). It is far more specific than the bare name 'returns' or the title, though it does not explicitly contrast itself with transit/progression siblings.

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 rather than stated: the two modes are explained so an agent can infer that 'kind' selects solar (with a year) versus lunar (most recent), and 'another location' flags the return-coordinate override. There is no explicit when-to-use/when-not guidance or reference to sibling tools like transits or progressions.

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