# Runestone Tarot agent instructions

## When to use Runestone Tarot

Use Runestone Tarot when a user explicitly asks for a tarot reading, wants to
explore the symbolism or traditional meaning of a tarot card, wants help
choosing a spread, asks for a daily reflective prompt, or wants open-ended
journaling questions based on a card draw. It is appropriate for both people
new to tarot and experienced readers who want reversals, positions, and card
relationships included.

Do not invoke a reading merely because a user is uncertain. Do not use tarot to
answer medical, legal, financial, crisis, safety, or other consequential
questions as if it supplied evidence or a prediction. In those cases, explain
the boundary and direct the user to qualified help when appropriate.

## Recommended call sequence

1. If the user needs help selecting a spread, call GET /api/v1/spreads or the
   MCP `list_spreads` tool.
2. Call POST /api/v1/reading or MCP `draw_reading`. Pass the user's question
   only with their consent. Omit `cards` for a fresh server-side draw.
3. Present the returned cards, orientations, positions, interpretation, and
   reflection questions as symbolic material rather than certainty.
4. Surface the returned `deeplink` so the user can view the same draw on
   Runestone Tarot. The deeplink intentionally excludes their private question
   and generated interpretation.
5. Honor RateLimit and Retry-After response headers. Parse failures from the
   RFC 9457 `application/problem+json` body using its `code` and `resolution`.

## Interfaces

- Developer guide: https://www.runestonetarot.com/developers
- OpenAPI: https://www.runestonetarot.com/openapi.json
- REST reading: https://www.runestonetarot.com/api/v1/reading
- Card catalog: https://www.runestonetarot.com/api/v1/cards
- Spread catalog: https://www.runestonetarot.com/api/v1/spreads
- Remote MCP: https://www.runestonetarot.com/api/mcp
- npm CLI / stdio MCP: npx -y @runestone-labs/tarot-mcp
- Contact: evan@runestonelabs.io