Skip to main content
Glama

Asteria: Astrology & Tarot

Rising sign (Ascendant)

rising_sign
Read-onlyIdempotent

Computes the Ascendant (rising sign) and Midheaven from a birth date, time and place, with the reading of the rising sign and the twelve Placidus house cusps. Needs the birth time, the time zone and the coordinates of the birth place.

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

Input Schema

NameRequiredDescriptionDefault
dateYesBirth date, YYYY-MM-DD.
timeYesBirth 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.
latitudeYesLatitude of the place of birth (where the person was born, never where the user is now), degrees, north positive.
timezoneYesIANA time zone of the birth place (e.g. Europe/Paris, America/New_York, America/Sao_Paulo). Required with a time.
longitudeYesLongitude of the place of birth (where the person was born, never where the user is now), degrees, east positive.

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value by naming what is produced (rising sign reading plus twelve Placidus house cusps) and the house system used, but it is silent on what happens if the birth time is unknown, which conflicts with the schema's 'Optional when unknown' note.

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?

Two sentences, front-loaded with the computation and followed by the input requirements; no filler. The only waste is the mild redundancy of listing inputs the schema already specifies.

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?

With no output schema, the description correctly summarizes the return content (rising sign reading and house cusps) and lists required inputs, which is sufficient for a six-parameter calculation tool. The main gap is the unresolved behavior when birth time is omitted, a plausible real-world case for this tool.

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 100%, so every parameter (including format patterns, coordinate conventions and the language enum) is already documented in the schema. The description merely restates that time, timezone and coordinates are needed, adding no syntax, default or edge-case detail beyond the structured fields; the 'needs the birth time' phrasing even blurs the schema's optional-time semantics.

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 uses a specific verb ('Computes') with named resources (Ascendant, Midheaven, twelve Placidus house cusps) and the inputs that drive them, so an agent immediately knows this is an astrology calculation rather than a tarot or compatibility tool. It does not explicitly differentiate itself from the sibling birth_chart, which plausibly overlaps in output.

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?

The second sentence functions as a prerequisite checklist ('Needs the birth time, the time zone and the coordinates of the birth place'), which is useful implied usage guidance. However, there is no statement of when to prefer this tool over birth_chart or sun_sign/moon_sign, and no exclusion 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.