Skip to main content
Glama

AstroWay Core astrology

Sabian Symbols

astroway_aspects_sabian_symbols
Read-onlyIdempotent

Return the Sabian degree for each given ecliptic longitude: sign (0 = Aries) and degree 1-30, the longitude rounded up, so 15.5 is Aries 16 and 0 is Pisces 30. The symbol text is not available: symbol is always null and textAvailable is false. Use the degree to look the symbol up in your own licensed text.

[Group: Aspects & Points] [Endpoint: POST /v1/sabian-symbols] [Required: longitudes] [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": {
      "longitudes": "<longitudes>"
    },
    "name": "astroway_aspects_sabian_symbols"
  }
}

Input Schema

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

Output Schema

NameRequiredDescriptionDefault
countNo
symbolsNo
textAvailableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / textAvailable
      Added value: +{
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
  2. Changed5 schema fields changed
    • removedInput schema / properties / longitudes / items / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / longitudes / items / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / count / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / count / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • changedOutput schema / properties / symbols / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "degree": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "longitude": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "sign": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "symbol": {
      -              "anyOf": [
      -                {},
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "degree": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "longitude": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "sign": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            },
      +            "symbol": {
      +              "anyOf": [
      +                {},
      +                {
      +                  "type": "null"
      +                }
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses a critical behavioral fact: symbol is always null and textAvailable is false, so the tool does not return the thing its name suggests. It also spells out the rounding convention (15.5 → Aries 16, 0 → Pisces 30) and the 10-credit Tier 1 cost, which is exactly the context an agent needs before spending credits.

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

Conciseness5/5

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

Four compact sentences, front-loaded with the core computation and immediately followed by the most surprising constraint (null symbol). Endpoint, required parameter, and cost are factored into bracketed metadata rather than prose, so nothing is wasted.

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

Completeness4/5

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

With an output schema present, return values need not be explained, yet the description still flags the null symbol and textAvailable fields and the credit cost. Minor gaps remain: it does not say whether null entries are permitted in the longitudes array or what happens at array limits, despite the schema allowing nullable items.

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

Parameters4/5

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

Schema coverage is 67% and the required longitudes array carries no schema description; the description compensates by explaining that each value is an ecliptic longitude mapped to sign (0 = Aries) and degree 1-30 with a round-up rule. It adds no meaning for fields or precision, but those are already documented in the schema.

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?

States a specific verb and resource ('Return the Sabian degree for each given ecliptic longitude') and defines the output fields sign and degree, so an agent knows exactly what computation is performed. It does not explicitly contrast itself with sibling lookup tools such as astroway_aspects_fixed_stars_catalog, so it falls short of full sibling differentiation.

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 final sentence ('Use the degree to look the symbol up in your own licensed text') gives downstream guidance on what to do with the result, which implies the intended workflow. However, it never states when to call this tool versus alternatives, nor any prerequisites or exclusions.

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