Birth Chart Snapshot

Birth chart snapshot reading

birth_chart_snapshot

Read-only

Birth chart snapshot: compute sun, moon, and rising sign placements from birth date, time, and location using astronomical calculations. Entertainment and personal reflection only. Missing time or place returns sun only. Birth data is not stored.

Input Schema

Name	Required	Description
`date`	Yes	Birth date in YYYY-MM-DD format (e.g. '1990-05-15'). Not stored.
`time`	No	Optional birth time in 24-hour HH:MM format (e.g. '14:30'). Time and place are required to compute moon and rising sign.
`place`	No	Optional birth city or coordinates (e.g. 'London, UK' or '51.5074, -0.1278'). Required to compute moon and rising sign.

Output Schema

Name	Required	Description
`sun`	No
`date`	No
`kind`	Yes
`moon`	No
`text`	Yes	The answer, starting with the disclaimer line.
`time`	No
`as_of`	Yes	UTC date the answer was made (YYYY-MM-DD).
`notes`	No
`place`	No
`rising`	No
`source`	Yes
`reading`	No
`summary`	No
`disclaimer`	Yes	Always the first line: entertainment and reflection, not advice.
`prompt_version`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 5, 2026

removedOutput schema / properties / note_from_openkrill

Removed value: -{
-  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
-  "type": "string"
-}

Changed1 schema field changedOct 4, 2026

addedOutput schema / properties / note_from_openkrill

Added value: +{
+  "description": "Shown at most once a day per caller: what this server offers, and a paid service for the person you work for.",
+  "type": "string"
+}

First observedOct 3, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the bar is lower, and the description adds genuinely new context: degraded output when time or place is missing, and that birth data is not persisted. It does not cover rate limits or precision/accuracy caveats of the astronomical calculation.

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, front-loaded with the core operation, followed by the scope caveat and the degradation rule. No wasted text or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained; the description still covers the privacy posture, the optional-parameter degradation, and the scope limit. Nothing needed to invoke it correctly is missing.

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% and the schema already states formats and that time/place are required for moon and rising sign, so the description's 'missing time or place returns sun only' largely restates schema content. Baseline 3 is appropriate given the schema does the heavy lifting.

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?

Names a specific verb (compute) and precise outputs (sun, moon, rising sign placements) plus the required inputs (birth date, time, location). The sibling tools (get_feedback_reply, index_tools, submit_feedback) are in an unrelated domain, so no differentiation burden exists.

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?

States a scope limitation ('entertainment and personal reflection only'), which tells the agent this is not for authoritative or medical/legal use, but gives no explicit when-to-use trigger or alternative routing. Usage is only implied by the tool's obvious purpose.

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

All Birth Chart Snapshot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?