Skip to main content
Glama
Sign In
Natal Chart Lab MCP

Natal Chart Lab MCP

by xucheng2024
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Current sky

get_current_sky
Read-only

Retrieve current tropical zodiac positions of the Sun, Moon and planets, plus Moon phase, illumination, retrograde status, and upcoming void-of-course windows in UTC.

Instructions

The sky right now: tropical zodiac sign and degree of the Sun, Moon and planets, the Moon's phase, illumination, next sign change and void-of-course windows for the next seven days, and which planets are retrograde or in shadow. Times are UTC.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail beyond that: the time convention (UTC), the seven-day forward window for void-of-course and sign changes, and the inclusion of retrograde/shadow flags. It does not describe return format or whether positions are geocentric, keeping it below 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 enumerating exactly what is returned, followed by a short UTC convention note. Nothing is redundant and the key scope is front-loaded.

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 parameters, no nested objects, and no output schema, the description covers what the tool returns and its time basis adequately. Minor gaps remain around output structure and geocentric vs. topocentric positioning, but an agent can call this correctly as-is.

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?

There are zero parameters, so per the rubric the baseline is 4. The description correctly adds the temporal scope (current moment plus seven-day lookahead) and timezone, which is meaningful context for a no-argument tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb-less but precise statement of the resource: planetary positions in the tropical zodiac, Moon phase, illumination, sign changes, void-of-course windows, and retrograde/shadow status. It distinguishes itself from siblings like get_planet_positions or get_retrogrades by being the combined real-time snapshot, and the 'right now' framing plus UTC note nails the scope.

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?

The phrase 'The sky right now' and 'next seven days' clearly delimits when this tool applies, implying siblings cover birth charts or narrower queries. It does not explicitly name alternatives or say when not to use it, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools