Skip to main content
Glama
astroway

astroway-mcp

Official

Geodetic Equivalents

geodetic
Read-onlyIdempotent

Convert geographic coordinates to geodetic zodiac degrees for astro-geographical mapping. Supports Sepharial and Johndro methods.

Instructions

Convert geographic coordinates to geodetic chart degrees (Sepharial method): each longitude maps to a zodiac degree on the Earth's surface.

[Group: Astro-Geography] [Cost: 10 credits (Tier 1)]

Example request body: {"latitude":50.45,"longitude":30.52}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYes
longitudeYes
methodNosepharial
yearNo
obliquityNo
Behavior3/5

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

Annotations already indicate readOnly, non-destructive, and idempotent behavior. The description adds that it uses the Sepharial method and maps longitude to zodiac degrees, providing moderate context beyond annotations.

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 short and includes a group label, cost, and example. It could be more concise by omitting the cost line, but overall it is fairly efficient.

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?

The description lacks explanation of what 'geodetic chart degrees' are, the output format, or how the optional parameters affect results. For a complex astro-geography tool without output schema, this is incomplete.

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?

With 0% schema description coverage for 5 parameters, the description only mentions latitude and longitude in the example, failing to explain method, year, or obliquity. This forces the agent to infer meaning, which is insufficient.

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 clearly states the tool converts geographic coordinates to geodetic chart degrees using the Sepharial method, mapping longitude to zodiac degrees. This is a specific verb+resource with clear scope.

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?

The description mentions the group 'Astro-Geography' and provides an example, but it does not explicitly differentiate this tool from sibling tools like acg or solar_acg. Usage context is implied but not directly addressed.

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