Skip to main content
Glama

Asteria: Astrology & Tarot

Moon sign

moon_sign
Read-onlyIdempotent

Finds the sign of the Moon at a birth and returns its reading (emotions, needs, what brings security). The Moon changes sign every two to three days: without a birth time, every sign it crossed that day is 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": "moon_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.4/5.0
Behavior4/5

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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavior beyond them: the Moon changes sign every two to three days, and without a birth time the tool returns every sign crossed that day. It stops short of detailing the exact return structure.

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, front-loaded with the core purpose and followed by the key behavioral caveat. Every sentence adds useful information without repetition.

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 four-parameter read-only tool with no output schema, the description covers purpose, reading content, and the no-time fallback. It does not specify the exact shape of the returned reading or mention that timezone is required with time, though the schema covers that requirement.

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 100%, so the baseline is 3. The description goes beyond the schema by explaining the consequence of omitting the birth time: multiple Moon signs may be returned. It does not add much about the timezone or language parameters beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: it finds the Moon sign at a birth and returns its reading. The Moon-specific focus clearly separates it from sun_sign and rising_sign even without naming those siblings.

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 clear context for when the tool applies: a birth Moon sign and its emotional/security reading. It also explains the no-birth-time case. It does not explicitly compare against alternatives such as birth_chart or sun_sign, so it falls short of full when/when-not guidance.

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.