> ## Documentation Index
> Fetch the complete documentation index at: https://docs.geometry.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Tools overview

> MCP tool catalog — what builders call.

# Tools

GEOMETRY exposes curated **tools** over MCP. Same engine on Path B HTTP later.

| Tool                                                      | Job                                                     |
| --------------------------------------------------------- | ------------------------------------------------------- |
| [`get_card_for_birthdate`](/tools/get-card-for-birthdate) | One birth date → full cosmic identity + temporal layers |
| [`get_compatibility`](/tools/get-compatibility)           | Two birth dates → scored compatibility read             |
| [`get_day_card`](/tools/get-day-card)                     | One calendar day → day card + day ruler                 |

Coming next (beta roadmap): name cards, birthday engine, team compatibility.

All string fields in tool JSON are **lowercase** except glyph fields. No nulls — sentinels like `none`, `0`, `[]`.

**Full payload / raw JSON:** same thing — the complete object the tool returns. There is **no** `full_payload` flag; each tool’s only levers are its date inputs. Builders integrating MCP/HTTP get the whole payload on the wire every time. Chat UIs may summarize what the agent already received — if you want it pasted verbatim, ask the agent to show the **raw tool result** (that instruction is to the model, not to GEOMETRY).