Skip to main content
Glama
astroway

astroway-mcp

Official

Quality of Time

hellenistic_greenbaum_quality_of_time
Read-onlyIdempotent

Assess the synchronistic quality of any moment using Hellenistic Greenbaum tradition astrology, providing insights based on date, time, and location.

Instructions

Synchronistic quality of a moment.

[Group: Hellenistic — Greenbaum tradition]

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

Input Schema

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

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

Description adds no behavioral traits beyond annotations (readOnlyHint, idempotentHint). 'Synchronistic quality' is not behavioral context.

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?

Very short, but does not waste words; however lacks substance. Could be more informative without increasing length.

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

Completeness1/5

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

No explanation of parameters, no output schema, and minimal description. Agent cannot understand what to provide or expect.

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

Parameters1/5

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

Schema has 11 parameters with 0% description coverage. Description does not explain any parameter; example mentions 'chart' which is not a schema parameter, misleading.

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

Purpose2/5

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

Description is vague: 'Synchronistic quality of a moment.' Does not state what the tool computes or returns. No differentiation from many Hellenistic Greenbaum siblings.

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 vs alternatives. No context or exclusions 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