Skip to main content
Glama

Ingresses, lunations and stations

timing_events
Read-onlyIdempotent

Between two dates: planets changing sign, new and full Moons (and quarters), and retrograde and direct stations, each with its exact moment in UTC. At most two years per call.

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

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
kindsNoDefault all three

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 cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower, and the description still adds real operational context: results are timestamped in UTC and the call is capped at a two-year span. It does not say what happens on an over-long range (error vs. truncation), which is the one remaining gap.

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?

Two sentences, zero filler, with the returned content front-loaded and the size limit as a trailing constraint. Every clause carries information.

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 takes on the burden of describing return content ('each with its exact moment in UTC'), which is sufficient for an agent to interpret results. The only shortfall is the unstated date-format expectation for the required 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 coverage is only 33%, and the description does not explain the from/to date format (the ±5-digit-year pattern is unstated in prose). It does earn credit for mapping the three enum values to concrete meanings — sign changes, lunations/quarters, and retrograde/direct stations — which the schema lists as bare strings, plus noting the default of all three.

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 the specific resource set — sign ingresses, new/full Moons and quarters, and retrograde/direct stations — with a clear verb-like framing ('Between two dates'). It is distinguishable from siblings such as eclipses or transits by content, though it never explicitly contrasts itself with them.

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?

'At most two years per call' is a useful operating constraint, and the date-range framing implies when the tool applies. However, there is no explicit guidance on when to choose this over eclipses or transits, nor any statement of prerequisites or exclusions.

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