Skip to main content
Glama
astroway

astroway-mcp

Official

ZR Loosing of Bond

hellenistic_brennan_zr_loosing_of_bond
Read-onlyIdempotent

Identify Loosing of Bond in ZR sequence for a given birth chart. Uses Hellenistic Brennan tradition to detect bond loosening events.

Instructions

Loosing of Bond detection within ZR sequence.

[Group: Hellenistic — Brennan tradition]

Example request body: {"...chart":"..."}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBirth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss). Defaults to lat/lon/tz=0 if omitted; pass real values for accurate computation.
Behavior2/5

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

Annotations already indicate read-only and idempotent behavior. The description adds no behavioral detail about what the detection returns or any side effects.

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

Conciseness3/5

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

The description is brief but lacks substance; the example is incomplete and does not aid understanding. Structure is minimal.

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?

For a niche astrological tool, the description fails to explain what 'loosing of bond' means, expected output, or conditions for use. Incomplete given complexity.

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 coverage is 100% with descriptions for each parameter. The description adds a vague example but no meaningful semantics beyond the schema.

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

Purpose3/5

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

The description states it detects 'loosing of bond' within the ZR sequence, but it does not explain what that means or differentiate from sibling tools like zodiacal_releasing_fortune or zr_peak_periods.

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 alternative Brennan ZR tools or other astrological tools. No context for appropriate scenarios.

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