Skip to main content
Glama

AstroWay Divination and esoterica

Angel Number Lookup

astroway_esoteric_angel_numbers_number
Read-onlyIdempotent

Look up the meaning of a specific angel number sequence. Falls back to numerological reduction if not in catalogue.

[Group: Esoteric] [Endpoint: GET /v1/esoteric/angel-numbers/{number}] [Required: number] [Cost: see your plan — endpoint not in the public credit manifest]

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": {
      "number": "<number>"
    },
    "name": "astroway_esoteric_angel_numbers_number"
  }
}

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.
numberYesAngel number, digits only. Unindexed numbers fall back to a pattern classification plus the reduced single digit.
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
numberNo
themesNo
matchedNo
patternNo
shortMeaningNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedOutput schema / properties / matched / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / matched / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / number / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / number / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / pattern / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / pattern / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / shortMeaning / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / shortMeaning / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / themes / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "type": "string"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact: unindexed numbers fall back to pattern classification plus reduced digit, which matters because openWorldHint=false implies a fixed catalogue. It says nothing about response shape, confidence, or how the fallback output differs, and the cost line only says cost is unknown.

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?

Two sentences, front-loaded with purpose then the fallback caveat, with no filler. The bracketed metadata block (group, endpoint, required param, cost caveat) is boilerplate but still carries signal about cost being unlisted.

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?

An output schema exists and annotations are rich, so the description need not explain returns or safety. It covers the one non-obvious behavior (catalogue miss handling) and the required input, leaving only minor gaps such as overlap with the decode sibling.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters carry their own descriptions, making 3 the baseline. The description's fallback sentence largely restates what the `number` schema description already says ("Unindexed numbers fall back to a pattern classification plus the reduced single digit") and adds nothing for `fields` or `precision`.

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 ("Look up the meaning of a specific angel number sequence") and the scope word "specific" separates it from the sibling listing tool astroway_esoteric_angel_numbers. It does not explicitly distinguish itself from astroway_esoteric_angel_numbers_decode or _by_life_path_n, so the sibling differentiation is incomplete.

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 usage context is only implied: you use it when you already have a numeric sequence to interpret. No explicit when-to-use versus when-not, and no routing to decode/by_life_path_variants, which plausibly overlap. The fallback clause hints at the acceptable input range but is not framed as 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