Skip to main content
Glama

counterfactual_chart

A birth chart, perturbed — a 'what if'. Give a base chart (date+lat+lon) and an edit: shift_time (e.g. '1h', '-30m', 'P1D') moves the instant ("born an hour later"), move_lat+move_lon recompute at another place, and/or set_longitudes moves bodies to new ecliptic degrees ("Mars in the next sign"). Returns the diff vs the original: bodies that changed sign or house, aspects gained or lost, and angles that changed sign. A time/place edit rotates the houses and angles while planets stay put; a longitude splice moves only those bodies and recomputes their aspects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latYesLatitude, north positive
lonYesLongitude, EAST positive (Americas are negative)
dateYesUTC date-time, ISO 8601, e.g. 1990-06-10T14:30:00Z. Convert local birth time to UTC first.
zodiacNotropical (default) or sidereal:<ayanamsa>tropical
move_latNoRecompute at this latitude instead of the birth latitude
move_lonNoRecompute at this longitude instead of the birth longitude
shift_timeNoDuration to shift the instant: '1h', '-30m', 'P1Y'
house_systemNoHouse system (default placidus). Case- and spacing-insensitive; valid: placidus, whole_sign, equal, porphyry, koch, regiomontanus, campanus, alcabitius, morinus, meridian, polich_page, vehlow (aliases like "whole sign" also work).placidus
set_longitudesNoMove bodies to these ecliptic longitudes in degrees, e.g. { "mars": 45 }

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully covers behavior: it returns a diff showing changes in sign, house, aspects, and angles. It explains the mechanics of time/place edits versus longitude splices.

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?

The description is well-structured, starting with purpose, listing edits, then explaining effects. It is concise with no wasted words.

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?

Despite no output schema, the description lists what the diff contains (bodies changed sign/house, aspects gained/lost, angles changed sign). It could detail the return format more, but it is sufficient for the complexity.

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

Parameters5/5

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

The description adds significant context beyond the schema: it explains how each edit (shift_time, move_lat/lon, set_longitudes) affects the chart. For example, it distinguishes between house/angle rotation and planet movement.

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 clearly states it is a 'what if' perturbation of a birth chart, listing three types of edits. It distinguishes itself from the sibling natal_chart and other tools by focusing on modifications.

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 description explains when to use this tool (to explore 'what if' scenarios) and gives concrete examples of edits. It does not explicitly contrast with alternatives, but the context with siblings makes it clear.

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.

TDQS

A3.9/5.0
Disambiguation5/5

Each tool has a highly specific and well-described purpose. Despite the large number, their functions are clearly distinct—e.g., natal_chart vs current_sky vs composite, or dasha vs firdaria vs profections vs releasing. The detailed descriptions prevent ambiguity.

Naming Consistency3/5

Names are consistently in snake_case but vary in style: some are noun phrases (natal_chart, cosmic_weather), some are verb-like (releasing, returns), and some are descriptive (aspect_patterns, find_aspect_dates). There is no strict verb_noun pattern, leading to moderate consistency.

Tool Count4/5

34 tools is high but appropriate for a comprehensive astrology API covering natal, transits, progressions, returns, synastry, time-lord techniques, sky events, and synthetic bodies. Each tool serves a specific niche, so the count feels justified rather than excessive.

Completeness5/5

The tool surface is extremely thorough, covering all major areas of astrology: chart generation, aspects, configurations, dignities, time-lord techniques (multiple systems), synastry, composite, progressions, returns, transits, sky events, rectification, electional, and synthetic bodies. No obvious gaps for the intended domain.