Skip to main content
Glama

The sky at a moment

sky_now
Read-onlyIdempotent

Where every planet is at a moment (now by default): sign, degree, retrograde, and the aspects between them. Give a place to add houses and angles. Works for any date from 13,200 BC to AD 17,191.

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

Input Schema

NameRequiredDescriptionDefault
latitudeNo
longitudeNo
datetime_utcNoThe moment in UTC, YYYY-MM-DDTHH:MM (default now)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-open-world, so the safety profile is covered. The description adds genuinely useful behavioral facts beyond that: an extremely wide supported date range, a default of 'now', and the fact that houses/angles are only computed when a place is provided. It does not specify coordinate reference or response shape, but that is a minor gap given the annotation coverage.

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?

Three short sentences, each carrying distinct information: output content, optional-place behavior, and supported date range. The most important fact (what you get back) is front-loaded, with no filler.

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 carries the burden of describing returns and does so reasonably (sign, degree, retrograde, aspects, plus houses/angles conditionally). It stops short of stating whether latitude and longitude must be supplied together or how to interpret a partial place, but the tool is simple enough that this is a small gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33%, with latitude and longitude undocumented in the schema, so the description must compensate. It does so by explaining that supplying a place unlocks houses and angles, and that datetime_utc defaults to now, which is meaningful semantics an agent cannot get from the bare numeric bounds.

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: returns where every planet is at a moment, including sign, degree, retrograde status, and aspects. 'Every planet' implicitly contrasts with the singular sibling planet_position, but no sibling is named, so the differentiation is left for the agent to infer.

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?

The conditional 'Give a place to add houses and angles' plus '(now by default)' gives real guidance about when to supply optional parameters. However, with nine siblings including natal_chart, transits, and planet_position, the description never says when to choose sky_now over those alternatives.

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