Skip to main content
Glama

Zodiac Compatibility

Find a Venus sign

find_venus_sign
Read-onlyIdempotent

Returns the sign Venus was in on a birth date, with its degree and whether it was retrograde. A date on which Venus changed sign returns both signs unless a birth time is given.

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>"
    },
    "name": "find_venus_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.
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.
birthTimeNoLocal birth time as HH:MM on a 24-hour clock.

Output Schema

NameRequiredDescriptionDefault
itemYes
viewYes
requestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is low; the description still adds real behavior by disclosing the cusp-date rule (both signs returned when no birth time is supplied). It stops short of saying what happens if place/timeZone are omitted, which matters for a non-required location parameter.

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 with no filler: the return shape comes first, then the one edge case. Nothing is repeated from the schema or annotations.

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?

Complete for the primary output and the ambiguous-date case, and the output schema removes any need to describe return structure. A sentence on whether place/timeZone are needed for the degree accuracy would close the remaining gap.

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 baseline is 3, but the description earns above baseline because it explains the functional role of birthTime — it disambiguates dates when Venus changes sign — which the schema alone (just 'HH:MM, 24-hour clock') does not convey.

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 sign Venus was in on a birth date') and names the payload ('degree and whether it was retrograde'). The planet Venus is named explicitly, which separates it from the sun/moon/rising siblings without needing to compare schemas.

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?

Provides the key usage condition for the birthTime parameter, but never states when to call this instead of find_sun_sign or get_birth_chart, nor any prerequisites. Usage is implied by the planet name rather than argued.

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.