astroway-mcp

Official

by astroway

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Natal texts (static)

astroway_reference_natal_texts

Read-onlyIdempotent

Retrieve edited natal-chart interpretation texts by key and language; unavailable language entries return in a missing list, never as fallback text.

Instructions

Edited interpretation texts for a chart, no AI at request time. keys is a comma list of up to 64: sun.aries (planet in sign, also chiron, ascendant), moon.h4 (planet in house), sun_moon.trine (major aspect between two of Sun..Pluto). lang is required; a text that does not exist in that language is listed in missing, never replaced by another language. Planet in sign covers 20 languages; houses and aspects are being written. Plain text, paragraphs separated by a blank line.

[Group: Reference] [Endpoint: GET /v1/natal-texts] [Required: keys, lang] [Cost: 10 credits (Tier 1)]

Keys with no text in the requested lang come back listed in missing, not in texts. Do not invent, translate or guess a replacement body for a key that comes back in missing; report it as unavailable.

Input Schema

Name	Required	Description	Default
`keys`	Yes	Comma list of up to 64 distinct keys: `<body>.<sign>` (planet in sign, also `chiron`, `ascendant`, `north_node`, `south_node`, `lilith`), `<body>.h<1-12>` (planet in house, also `chiron`, `lilith`), `<body>_<body>.<aspect>` (conjunction, sextile, square, trine, opposition between two of Sun..Pluto), `pattern.<name>` (t_square, grand_trine, grand_cross, stellium, yod, kite; kind `pattern`, a general text for the figure, the planets are yours to list). Nodes, Lilith in sign and patterns are written in every language listed for `lang`.
`lang`	Yes	Language of the texts. No fallback: a text missing in this language is listed in `missing`.

Output Schema

Name	Required	Description	Default
`lang`	No
`texts`	No
`missing`	No

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.6.0Oct 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the read-only, idempotent annotations, the description discloses crucial behavior: missing-language texts are returned in a `missing` list with no fallback, the agent must never invent or translate replacements, language coverage differs by key type, and responses are plain text with blank-line-separated paragraphs. It also surfaces cost (10 credits).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and key-format details are front-loaded and the bracketed metadata is easy to scan. There is mild redundancy: the missing-language fallback behavior is stated in the first paragraph and again in the final paragraph, costing some conciseness.

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?

Given the output schema exists, the description does not need to explain return fields. It nevertheless covers everything an agent needs: key syntax, language fallback, missing-key handling, output format, and cost, complementing the read-only annotations fully.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds useful semantics beyond the schema by noting that planet-in-sign texts cover 20 languages while house and aspect texts are still being written, clarifying what the `keys` parameter can practically retrieve.

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?

States a specific resource (edited interpretation texts for a chart) and scope (no AI at request time), which distinguishes it from AI-interpretation siblings such as astroway_ai_interpret_natal. An agent can tell exactly what it returns without opening the schema.

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 phrase 'no AI at request time' gives clear context for when this static-text tool is appropriate rather than an AI interpretation endpoint. However, it does not explicitly name an alternative sibling or state when not to use it, leaving the routing decision partially implicit.

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

Deploy Server