Skip to main content
Glama

NatalChart.AI Astrology

Solar return

solar_return
Read-onlyIdempotent

The solar return chart for a year, cast for the birth place or another location. (Premium or MAX) Use it for the year ahead from a birthday; it needs a birth time.

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": {
      "birth": "<birth>",
      "year": "<year>"
    },
    "name": "solar_return"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYes
birthYes
locationNo

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 readOnlyHint, idempotentHint, and openWorldHint=false. The description adds the Premium/MAX access requirement and birth-time prerequisite, but does not explain null-time behavior or what the chart output contains.

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, front-loaded with the purpose and use case. The Premium/MAX parenthetical is brief and does not disrupt readability.

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?

Covers the core use case and key prerequisite, but for a nested 3-parameter chart tool with no output schema it omits year bounds, timezone handling, and what happens when birth time is null.

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 0% per the provided context, so the description must compensate. It only clarifies the birth-time requirement and the optional alternate location, leaving year bounds, birth date, coordinates, and timezone semantics undocumented in 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?

States that it computes a solar return chart for a given year and can cast it for the birth place or another location. The verb/resource is clear, but it does not explicitly distinguish itself from siblings like natal_chart or transits beyond the year-ahead use case.

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?

Explicitly says to use it for the year ahead from a birthday and notes that a birth time is required. It gives clear context but does not name alternatives or when-not-to-use conditions.

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