Skip to main content
Glama

Your birthday

get_birthday
Read-only

Describes the sky on a birthday: the Sun's sign for the date, its traditional meaning, the decan, and whether the date is on a cusp where the sign depends on the year or time. With a full birth date it resolves a cusp date's sign for that year, or calculates a solar return, the moment the Sun comes back to its birth position. It links to the date's birthday page and names the published famous people born that day. It fits a question about one birthday. It makes no prediction. A month and day is enough for general facts; the full birth date is needed only for a cusp or a solar return. The longitude field is for historical dates when a birthplace kept local mean time, and has no use for a modern birthday. Solar return years run from 1801 to 2199. It refuses a birth date less than 13 years ago. Its share link carries the month and day, never the year.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_birthday"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoA birthday without a year, as MM-DD, such as 05-03 for 3 May. This is enough for general birthday facts. Give this or birthDate.
timeNoThe birth time on the local clock, if known. Needs zone.
yearNoThe year of the solar return. Defaults to the current year. Needs birthDate.
zoneNoThe birthplace's time zone, such as Europe/London.
birthDateNoThe full birth date, such as 1997-05-03. Use only for the solar return or to resolve the sign of a cusp date in that birth year.
longitudeNoUse only for historical birth dates when the birthplace used local mean time, to convert its clock to UTC. Needs zone. Do not request coordinates for modern birthdays.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, and the description adds real context on top: no predictions are made, recent birth dates are refused, solar return years are bounded 1801–2199, and the share link deliberately omits the year for privacy. The only gap is that it does not say what happens when an optional parameter is supplied without its dependency (e.g., time without zone) — though the schema covers that pairing.

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?

It is long — nine sentences — but nearly every one carries a distinct constraint (cusp handling, refusal rule, year bounds, privacy of the share link). The one soft sentence is 'It fits a question about one birthday,' which could be folded into the opening, and the ordering mixes capability description with usage rules mid-paragraph.

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?

For a six-parameter read-only lookup with an output schema, the description covers the capability, the parameter-selection logic, the refusal case, the valid year range, and the privacy behavior of the generated link. Nothing an agent needs in order to call it correctly or explain the result is missing.

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, but the description adds cross-parameter decision logic the schema states only per-field: which single date form is sufficient, when the full birth date becomes necessary, and that longitude is useless for modern birthdays. This helps the agent choose a parameter combination rather than read fields in isolation.

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 names a concrete resource and enumerates exactly what is produced: the Sun's sign for the date, its traditional meaning, the decan, cusp status, an optional solar return, a link to the date's birthday page, and famous people born that day. It also draws a firm boundary — 'It fits a question about one birthday. It makes no prediction' — which separates it from natal-chart and horoscope siblings.

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

Usage Guidelines5/5

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

It gives explicit selection rules: a month and day suffices for general facts, the full birth date is required only for a cusp resolution or a solar return, and longitude applies only to historical dates using local mean time. It even states a refusal condition (birth dates under 13 years) and a validity range (1801–2199), so the agent knows both when to call and when not to.

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.