Skip to main content
Glama

The sky on a day

get_occasion_sky
Read-onlyIdempotent

Describes the sky on a day that matters to someone: the Sun and Moon signs, the Moon's phase and any retrograde planets, with a card title and short lines. With a place it adds sunset, golden hour, dusk, the Moon and the planets visible that evening. It rates the date from 0 to 100 with a verdict, the astrological reasons (Venus, the Moon's phase and sign, retrograde planets) and a "Reading confidence NN%" label that says how specific the details were, not the odds of an event. Given a window of up to 92 days as searchFrom and searchTo it rates every day and returns the three best-rated days. It rates one date per call. cardUrl is the complete link to the printable card, including every field after #; when cardUrl is null, the returned page link takes its place. shareUrl is the link for sharing the rating. It fits a wedding, an anniversary, the day two people met, a birthday, a pet, a new home, a job, a graduation, a retirement or a gathering. The rating is astrology's traditional reading; it never guarantees how the day will go. A birthday card for a day in the last 13 years is refused. A card's link carries the occasion's own day, time, zone and rounded coordinates, and no name. The place name and first names are printed on the card only and are not used in the calculation.

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": {
      "occasion": "<occasion>"
    },
    "name": "get_occasion_sky"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoThe day, such as 2027-09-18 (years 1800–2199). Needed unless searchFrom and searchTo are given.
timeNoThe local clock time, such as 16:30, if the person gives one. Needs zone.
zoneNoThe place's time zone, such as Europe/Lisbon. Needed with a time or a place.
namesNoOptional: up to two first names to print on the card, only if the person asks for them. Display only, not stored.
placeNoOptional place name printed on the card, such as Lisbon, Portugal. Display only: it is not used in the calculation and is not stored.
latitudeNoOptional. The place's latitude, used only to work out sunset, golden hour and the evening sky there. Give it with longitude and zone. Nothing is stored.
occasionYesWhat the day is: wedding, anniversary, met (the day they met), birthday, pet, home, job, graduation, retirement or gathering.
searchToNoThe last day of the window to search, such as 2027-09-30, at most 92 days after searchFrom counting both days. Every day is rated and the three best come back.
longitudeNoOptional. The place's longitude, with latitude, for the evening sky. Nothing is stored.
searchFromNoTo find the best days: the first day of the window to search, such as 2027-09-01. Give it with searchTo.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / date / description
      Previous value: -"The day, such as 2027-06-12 (years 1800–2199). Needed unless searchFrom and searchTo are given."New value: +"The day, such as 2027-09-18 (years 1800–2199). Needed unless searchFrom and searchTo are given."
    • changedInput schema / properties / place / description
      Previous value: -"Optional place name printed on the card, such as Florence, Italy. Display only: it is not used in the calculation and is not stored."New value: +"Optional place name printed on the card, such as Lisbon, Portugal. Display only: it is not used in the calculation and is not stored."
    • changedInput schema / properties / searchFrom / description
      Previous value: -"To find the best days: the first day of the window to search, such as 2027-06-01. Give it with searchTo."New value: +"To find the best days: the first day of the window to search, such as 2027-09-01. Give it with searchTo."
    • changedInput schema / properties / searchTo / description
      Previous value: -"The last day of the window to search, such as 2027-06-30, at most 92 days after searchFrom counting both days. Every day is rated and the three best come back."New value: +"The last day of the window to search, such as 2027-09-30, at most 92 days after searchFrom counting both days. Every day is rated and the three best come back."
    • changedInput schema / properties / time / description
      Previous value: -"The local clock time, such as 19:00, if the person gives one. Needs zone."New value: +"The local clock time, such as 16:30, if the person gives one. Needs zone."
    • changedInput schema / properties / zone / description
      Previous value: -"The place's time zone, such as Europe/Rome. Needed with a time or a place."New value: +"The place's time zone, such as Europe/Lisbon. Needed with a time or a place."
  2. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations only declare read-only/idempotent/non-destructive, and the description goes well beyond them: it explains the 0–100 rating plus verdict, defines the 'Reading confidence NN%' label as a specificity measure rather than odds, explains cardUrl vs its null fallback and shareUrl, discloses the 13-year birthday refusal, and states the disclaimer that the rating never guarantees the day. It also discloses data handling — names and place are display-only and not used in the calculation, and the link carries rounded coordinates and no name — which is exactly the kind of context an agent needs and the schema does not provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first two sentences and the writing is organized roughly by mode, output, and caveats. However the description runs long for a single tool, mixing output-link mechanics (cardUrl null fallback, shareUrl) into the body and repeating constraints already encoded in the schema, which makes it denser than it needs to be.

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 10-parameter tool with an output schema, the description covers the modes, the refusal rule, privacy behavior, and the interpretation of the rating and confidence label, so an agent can invoke it correctly. The remaining gaps are the missing differentiation from the near-sibling sky tools and no guidance on error behavior beyond the birthday refusal.

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 coverage is 100%, so the schema already documents every parameter including the display-only caveats for names and place, so the baseline is 3. The description adds a little meaning beyond it, chiefly the mutual exclusivity of the single-date mode versus searchFrom/searchTo ('It rates one date per call') and the 92-day window semantics, but most parameter explanation is duplication of the schema text.

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?

Specific verb and resource: it 'describes the sky on a day that matters to someone', enumerates what is produced (Sun/Moon signs, phase, retrogrades, sunset/golden hour, a 0–100 rating, card and share links) and states the two operating modes (one date, or a searchFrom/searchTo window). What holds it at 4 is that it never distinguishes itself from the similar-sounding get_sky or get_sky_calendar, so an agent must guess which of the three to pick.

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?

Clear usage context: 'It fits a wedding, an anniversary, the day two people met, a birthday, a pet, a new home, a job, a graduation, a retirement or a gathering', plus the operational rule 'It rates one date per call' and the window mode limited to 92 days returning the three best days. Exclusions exist for a single edge case ('A birthday card for a day in the last 13 years is refused') but no alternative siblings are named for when this tool is the wrong choice.

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.