Skip to main content
Glama
astroway

astroway-mcp

Official

Witte Formulas

cosmobiology_witte_formulas
Read-onlyIdempotent

Calculate Witte planetary pictures (A+B−C=D) for cosmobiological analysis using birth data.

Instructions

Witte planetary pictures A+B−C=D.

[Group: Cosmobiology / Hamburg School]

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

Input Schema

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

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

Annotations already indicate readOnlyHint true and idempotentHint true, so the tool is a safe read operation. The description adds no additional behavioral traits, such as data requirements, rate limits, or side effects. It merely restates the calculation formula.

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

Conciseness2/5

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

The description is very short, but its brevity comes at the expense of essential information. It front-loads the formula but lacks structure and completeness. The placeholder example is not useful.

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?

Given 12 parameters, no output schema, and numerous sibling tools, the description is severely incomplete. It does not describe the output, differentiate from similar tools like cosmobiology_midpoint_pictures, or provide any context on how the parameters interact.

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 description coverage is 0%, and the description fails to compensate. It does not explain any of the 12 parameters, including critical ones like date, time, zodiacType, or cosmogram. The example request body is a placeholder with no detail. The AI agent gets no meaningful parameter guidance.

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 mentions 'Witte planetary pictures A+B-C=D' and groups it under Cosmobiology, giving a formula. However, it does not clearly define what a Witte planetary picture is or what the tool computes. It provides some specificity but lacks a clear statement of the tool's function for an AI agent.

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 is provided on when to use this tool versus its many cosmobiology siblings. The description does not mention prerequisites, appropriate contexts, or alternatives. It simply states the formula and group.

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