Skip to main content
Glama

Zodiac Compatibility

Find a rising sign

find_rising_sign
Read-onlyIdempotent

Returns the rising sign (Ascendant) with its degree, and the Descendant, Midheaven and Imum Coeli signs, for a birth date, time and place. Notes when the Ascendant lies within 1.5 degrees of a sign boundary.

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": {
      "birthDate": "<birthDate>",
      "birthTime": "<birthTime>"
    },
    "name": "find_rising_sign"
  }
}

Input Schema

NameRequiredDescriptionDefault
placeNoA city from the website's list of 67 places, in any letter case, such as London, New York, Tokyo, Sydney or Mumbai.
latitudeNoBirthplace latitude in degrees, north positive.
timeZoneNoAn IANA time zone name such as Europe/London, used instead of a city's zone.
birthDateYesBirth date as YYYY-MM-DD, from 1900 to 2100.
birthTimeYesLocal birth time as HH:MM on a 24-hour clock.
longitudeNoBirthplace longitude in degrees, east positive.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestNo

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 disclosing the 1.5-degree cusp warning behavior, which is domain behavior an agent could not infer. It says nothing, however, about how place vs latitude/longitude vs timeZone are reconciled, or what happens when the place is not one of the 67 supported cities.

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, zero filler. The primary return (rising sign + degree) is front-loaded, with secondary returns and the cusp caveat following in logical order.

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?

The output schema exists, so return values need not be spelled out, yet the description still summarizes them adequately. The gap is geographic resolution: birthLocation pieces are optional in the schema while the description implies place is required, leaving an agent unsure how to satisfy the location requirement. For a six-parameter tool with four optional geolocation fields, that ambiguity matters.

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 each of the six parameters (including the 67-city place list, IANA timeZone, and lat/long bounds) is already documented. The description only restates "birth date, time and place" and adds no new parameter meaning — notably it does not resolve the precedence between place, latitude/longitude and timeZone. Baseline 3 applies.

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?

States a specific verb and resource ("Returns the rising sign (Ascendant)") and extends it to the three angle signs (Descendant, Midheaven, Imum Coeli) plus degree. This is unambiguously distinct from find_sun_sign / find_moon_sign / get_birth_chart, so an agent can select it without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use or when-not-to-use guidance. It never says to prefer get_birth_chart when the full chart is wanted, nor when this single-angle lookup is the right choice over its siblings. Only the implied input context ("for a birth date, time and place") hints at usage.

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.