Skip to main content
Glama

ephemeris_bi_wheel

Read-only

Generate a bi-wheel SVG comparing two charts for synastry or transit analysis, with Subject A's planets on the inner wheel and Subject B's on the outer wheel. Requires birth data for both subjects.

Instructions

Generate a Bi-Wheel (Synastry/Transit) image (SVG) comparing two charts. Draws Subject A's planets on the inside wheel and Subject B's on the outside wheel. Returns a native SVG that Claude displays inline in the conversation.

CREDIT COST: 2 credits per call.

EXAMPLE: Compare someone born April 15, 1990 (A) to someone born June 10, 1992 (B): datetime_a='...', latitude_a=..., longitude_a=..., datetime_b='...', latitude_b=..., longitude_b=...

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datetime_aYesISO 8601 datetime string, e.g. '1990-04-15T14:30:00' (local time at birth location). Include timezone offset if known, e.g. '1990-04-15T14:30:00-05:00'.
timezone_aNoIANA timezone name for subject A, e.g. 'America/Denver'.
latitude_aYesLatitude for subject A
longitude_aYesLongitude for subject A
datetime_bYesISO 8601 datetime string, e.g. '1990-04-15T14:30:00' (local time at birth location). Include timezone offset if known, e.g. '1990-04-15T14:30:00-05:00'.
timezone_bNoIANA timezone name for subject B, e.g. 'Europe/London'.
latitude_bYesLatitude for subject B
longitude_bYesLongitude for subject B
house_systemNoHouse system to use. Defaults to 'placidus' if omitted.
styleNoAesthetic style of the chart: 'light' (default, warm cream background), 'dark' (deep navy), or 'mono' (black-and-white print-ready).
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful behavioral details: credit cost, output format (SVG) and inline display. No contradictions.

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?

Five sentences including a concrete example. No filler; front-loaded with core purpose. Every sentence adds value.

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?

For a tool with 10 parameters and no output schema, the description covers output format, credit cost, and usage example. Missing guidance on when to use this over related synastry/transit tools.

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 100%, so baseline is 3. Description includes an example with placeholders but does not add new semantic information beyond the schema descriptions.

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?

Clearly states it generates a Bi-Wheel SVG comparing two charts, explains layout (Subject A inside, Subject B outside), and notes it returns SVG inline. This distinguishes it from sibling tools like ephemeris_synastry or ephemeris_transits.

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?

Provides context that it is for synastry/transit comparisons and gives an example, but does not explicitly differentiate from similar sibling tools (e.g., ephemeris_synastry, ephemeris_overlay) or state when not to use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/openephemeris/openephemeris-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server