Skip to main content
Glama

Eclipses

eclipses
Read-onlyIdempotent

Solar and lunar eclipses between two dates (up to 20 years per call), with type, the exact moment of greatest eclipse and the eclipse degree. Works across the full 15,000-year span.

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "eclipses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond them: the 20-year-per-call cap, the full 15,000-year supported span, and what each result contains. It doesn't mention ordering, pagination or empty-result behavior, keeping it below 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.

Conciseness5/5

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

A single dense sentence front-loads the resource and range, then appends the returned fields and the global span. No filler, nothing redundant with structured data.

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?

With no output schema, the description correctly summarizes the return payload (type, greatest eclipse moment, eclipse degree), and annotations cover safety. Complete enough to call correctly; the only remaining gap is date-format and range-boundary semantics for the zero-coverage parameters.

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 0%, so the two date parameters rely entirely on the description and the pattern. The description supplies the essential semantics — from/to are a bounded date range with a 20-year maximum width — but gives no format guidance (e.g. signed years for BCE) or inclusive/exclusive boundary rules.

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?

States a specific verb and resource: it returns solar and lunar eclipses within a date range, plus the fields returned (type, greatest eclipse moment, eclipse degree). It is clearly a distinct astronomical lookup from siblings like transits or planet_position, though it doesn't name an alternative to route against.

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?

Usage constraints are embedded — 'between two dates', 'up to 20 years per call', 'full 15,000-year span' — which tells the agent the valid call shape. However, there is no explicit statement of when to prefer this over siblings such as timing_events or transits, so routing is left to inference.

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