Skip to main content
Glama
astroway

astroway-mcp

Official

Mutual Receptions

receptions
Read-onlyIdempotent

Identify planet pairs in mutual reception: each planet in a sign ruled or exalted by the other. Input birth data to analyze reciprocal dignities.

Instructions

Find mutual receptions between planets — pairs where each planet is in a sign ruled, exalted, or in the dignity of the other.

[Group: Dignities & Receptions] [Cost: 20 credits (Tier 2)]

Example request body: {"date":"1990-05-15","time":"14:30:00","timezoneOffset":3,"latitude":50.45,"longitude":30.52}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
timeYes
timezoneOffsetNo
latitudeNo
longitudeNo
houseSystemNoP
nameNo
cityNo
zodiacTypeNo
ayanamsaIdNo
cosmogramNo
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description does not need to restate safety. The description adds the definition of mutual receptions but does not disclose any additional behavioral traits (e.g., what happens if no receptions found, output format). With annotations covering core traits, a '3' is appropriate.

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 description is concise, with a clear first sentence defining the tool, followed by group and cost metadata and an example. Every sentence contributes, though the group/cost lines could potentially be in annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters, no output schema, and a specialized astrological concept, the description is too brief. It lacks details on output interpretation, edge cases, and parameter usage, making it incomplete for an agent to use effectively.

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

Parameters2/5

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

Schema description coverage is 0%, meaning the description provides no explanations for the 11 parameters. The example shows some parameters but does not clarify their meanings or constraints. The description fails to compensate for the missing schema documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it finds mutual receptions between planets and defines the concept. However, it does not differentiate from sibling tools in the 'Dignities & Receptions' group, such as essential_dignities or disposition_chains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. The group label implies context, but no explicit when-to-use or when-not-to-use instructions are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server