AstroWay Astrology API (full catalogue)

Crystals by Planet

astroway_esoteric_crystals_by_planet_planet

Read-onlyIdempotent

Crystals whose traditional planetary correspondence is the given planet (sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, earth).

[Group: Esoteric] [Endpoint: GET /v1/esoteric/crystals/by-planet/{planet}] [Required: planet] [Cost: see your plan — endpoint not in the public credit manifest]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "planet": "<planet>"
    },
    "name": "astroway_esoteric_crystals_by_planet_planet"
  }
}

Input Schema

Name	Required	Description
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`planet`	Yes	Planet name, case-insensitive.
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`count`	No
`items`	No
`planet`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish the safe read-only, idempotent, closed-world profile, so the description only needs to add context beyond that. It does add two useful facts the annotations cannot convey: the concrete endpoint path and a cost caveat ('endpoint not in the public credit manifest'), which warns the agent that billing for this call is uncertain. It stops short of describing result shape, but an output schema exists to cover that.

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 core purpose sentence is front-loaded and wastes no words, and the bracketed metadata block is scannable. The planet enumeration is duplicated from the schema enum, which is mild redundancy, but it aids quick selection.

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?

For a simple single-filter lookup with full schema coverage, complete annotations, and an output schema, nothing an agent needs in order to call this correctly is missing. Filter semantics, accepted values, and the billing caveat are all present.

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 description coverage is 100%, including the enum of eleven planets, the compact-mode 'fields' path syntax, and the 'precision' rounding semantics, so the schema does the heavy lifting. The description only restates the planet list and the '[Required: planet]' marker, adding no meaning beyond structured data, which matches the baseline 3.

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 gives a specific verb-free but precise resource statement: crystals filtered by traditional planetary correspondence, and it enumerates the valid planets inline. That distinguishes it cleanly from the neighbouring crystals_by_chakra, crystals_by_purpose, crystals_by_zodiac_sign, and plain crystals tools without the agent needing to open any schema.

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?

Usage is only implied: an agent can infer 'call this when you want crystals tied to a planet' from the filter semantics. There is no explicit when-to-use/when-not guidance and no pointer to the sibling tools for chakra, purpose, or zodiac lookups, so disambiguation is left to the agent.

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

All AstroWay Astrology API (full catalogue) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?