Skip to main content
Glama

Sky calendar for your calendar app

get_sky_calendar
Read-only

Returns the link for subscribing to Zodiacs' sky calendar in Google Calendar, Apple Calendar or Outlook, with how to add it and the next few events. The calendar holds new and full Moons, eclipses and retrograde periods and updates itself. It fits someone who wants these events in their own calendar. Event titles come in English, Spanish, Portuguese, French, Italian or Russian. It returns a subscription link; it adds nothing to anyone's calendar itself and schedules nothing.

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_sky_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoThe language of the event titles: en (the default), es, pt, fr, it or ru.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and destructiveHint=false, but the description goes further by explicitly denying side effects ('adds nothing to anyone's calendar itself and schedules nothing') and explaining that the returned calendar is self-updating because it is maintained externally. That is genuinely useful behavioral context not present in the annotations. It says nothing about rate limits or whether the link is personalized, which keeps it from a 5.

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?

The core capability is front-loaded in the first sentence, and the language note and no-side-effects clarification follow in a logical order. Three sentences is reasonable, though 'It fits someone who wants these events in their own calendar' is the weakest and partly redundant with the surrounding statements.

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?

This is a low-complexity, single-optional-parameter, read-only tool with an output schema, so the description need not document return structure — yet it still sketches the payload (link, instructions, next few events). It covers contents, audience, languages, and the absence of side effects, leaving nothing an agent needs in order to call it correctly.

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?

With a single optional parameter at 100% schema description coverage, the schema already documents the enum, the default, and that it controls event titles. The description's sentence 'Event titles come in English, Spanish, Portuguese, French, Italian or Russian' largely restates the enum rather than adding format, fallback, or precedence semantics. Baseline 3 is appropriate.

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 precise verb and resource: 'Returns the link for subscribing to Zodiacs' sky calendar in Google Calendar, Apple Calendar or Outlook.' It further specifies the payload (subscription link, how-to, next few events) and calendar contents (new/full Moons, eclipses, retrogrades). It never names a sibling tool, so it does not explicitly differentiate itself from get_sky, get_occasion_sky, or get_upcoming_events.

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?

'It fits someone who wants these events in their own calendar' gives a clear usage condition, and 'it adds nothing to anyone's calendar itself and schedules nothing' rules out the scheduling interpretation an agent might otherwise form. It stops short of naming an alternative tool for agents who want events listed directly rather than a subscription link.

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.