Skip to main content
Glama

Asteria: Astrology & Tarot

Zodiac sign (Sun sign)

sun_sign
Read-onlyIdempotent

Finds the zodiac sign (Sun sign, star sign) of a birth date and returns its reading: personality, strengths, what holds one back, what helps. On a day when the Sun changes sign, give the birth time and time zone to settle it; otherwise both possible signs are returned.

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>"
    },
    "name": "sun_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeNoBirth time on the local clock of the birth place, HH:MM (24-hour). Optional when unknown.
languageNoLanguage of the readings: en, fr, es, pt-BR, ja or de (default en). Use the language of the conversation.
timezoneNoIANA time zone of the birth place (e.g. Europe/Paris, America/New_York, America/Sao_Paulo). Required with a time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. Beyond that, the description discloses the non-obvious fallback behavior — ambiguous cusp dates return BOTH possible signs — which an agent could not infer from the schema or annotations and which affects how it should present results.

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 sentences, zero filler. The core purpose and return value come first, and the edge-case instruction follows — exactly the right order for an agent scanning for 'what does this do' before 'what do I need to pass'.

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

Completeness5/5

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

With no output schema, the description must say what comes back, and it does: a reading covering personality, strengths, obstacles and supports. Combined with the cusp-day ambiguity rule and a fully documented four-parameter schema, an agent has everything needed to invoke this correctly.

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 coverage is 100%, so every parameter is already documented, and the baseline is 3. The description only adds conditional weight to time/timezone (they matter only around a sign change), without elaborating on date format, enum values, or the language inheritance rule beyond what the schema states.

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 states a specific verb and resource — 'finds the zodiac sign (Sun sign, star sign) of a birth date' — and even summarizes the payload it returns (personality, strengths, blockers, helpers). The parenthetical synonyms 'Sun sign, star sign' implicitly separate it from moon_sign and rising_sign, 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 Guidelines4/5

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

It gives concrete conditional guidance: on a day when the Sun changes sign, supply birth time and time zone; otherwise both possible signs come back. That is real when-to-do-what guidance tied to input conditions, but there are no exclusions or pointers to alternative tools (e.g. moon_sign) for a different question.

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.