Skip to main content
Glama

AstroWay Core astrology

Geodetic Equivalents

astroway_geo_geodetic
Read-onlyIdempotent

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

[Group: Astro-Geography] [Endpoint: POST /v1/geodetic] [Required: latitude, longitude] [Cost: 10 credits (Tier 1)]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "astroway_geo_geodetic"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo
fieldsNoCompact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
methodNosepharial
latitudeYes
longitudeYes
obliquityNo
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

NameRequiredDescriptionDefault
geodeticMCNo
geodeticAscendantNo
zodiacalLongitudeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / properties / geodeticAscendant / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / geodeticAscendant / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / geodeticMC / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / geodeticMC / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / zodiacalLongitude / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / zodiacalLongitude / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context — the endpoint, the credit tier (10 credits, Tier 1), and the required inputs — but says nothing about the two methods in the enum or how output is shaped beyond what the output schema covers.

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?

A single front-loaded sentence conveys the operation and its geometric meaning, followed by a compact metadata block. No wasted prose, though the metadata lines could be folded more tightly.

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

Completeness3/5

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

An output schema exists, so return values need no explanation, and the safety profile is handled by annotations. What is missing for a 7-parameter tool is any account of the year/obliquity inputs, the method trade-off, and when this conversion is the right choice over sibling geo tools.

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 only 29%, so the description must compensate, and it largely does not: it mentions latitude/longitude and the Sepharial method, but leaves 'year' and 'obliquity' entirely unexplained in both schema and description. It also omits the 'johndro' alternative that the method enum exposes, so an agent cannot judge what that option changes.

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 uses a specific verb and resource ('Convert geographic coordinates to geodetic chart degrees') and explains the underlying transform ('each longitude maps to a zodiac degree on the Earth's surface'). It is clearly distinguishable from siblings like geo_reverse or geo_acg, though it never names those alternatives explicitly.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many geo_* siblings (geo_reverse, geo_zenith, geo_relocation). The metadata block lists required parameters and a credit cost, but that is invocation bookkeeping rather than usage selection guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources