Skip to main content
Glama

Rosmaryn

Upcoming sky events

upcoming_sky_events
Read-only

Upcoming Moon phases, eclipses, planets entering signs and retrograde stations (tropical zodiac, times in UTC), as published in the Rosmaryn sky calendar.

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": "upcoming_sky_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow many days ahead (default 30).
languageNoLanguage of the results (default en).
moon_onlyNoOnly Moon phases and eclipses.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already establish read-only and closed-world behavior. The description adds useful domain context beyond annotations: tropical zodiac, UTC times, and the Rosmaryn sky calendar source, but it does not describe output ordering, event precision, or response shape.

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?

The description is a single dense sentence that front-loads the event categories and then supplies conventions. There is no redundant or filler wording.

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 tool is simple and the input schema is fully documented, but there is no output schema and the description does not explain the returned event structure or ordering. It is adequate but leaves a meaningful gap for an agent that needs to understand the response.

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 the input schema already documents days, language, and moon_only. The description does not elaborate on parameter behavior, so the baseline score of 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 names specific event types (Moon phases, eclipses, planets entering signs, retrograde stations) and states the astrological frame and time basis. It is clearly an upcoming-events listing tool, though it does not explicitly distinguish itself from sibling tools.

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?

It implies the tool is for upcoming sky events but offers no explicit when-to-use guidance, exclusions, or alternatives. The agent must infer usage from the event list alone.

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.

Resources