Skip to main content
Glama

AstroWay Divination and esoterica

Daily Angel Number

astroway_esoteric_angel_numbers_today
Read-onlyIdempotent

Compute today's personal angel number from date (digit-sum reduced to single digit). Optional ?date=YYYY-MM-DD query.

[Group: Esoteric] [Endpoint: GET /v1/esoteric/angel-numbers/today] [Cost: 5 credits (Tier ½)]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "astroway_esoteric_angel_numbers_today"
  }
}

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.

Output Schema

NameRequiredDescriptionDefault
dateNo
meaningNo
dailySumNo
reducedToNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / properties / dailySum / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / dailySum / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / meaning / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": {},
      -    "properties": {
      -      "shortMeaning": {
      -        "anyOf": [
      -          {
      -            "type": "string"
      -          },
      -          {
      -            "type": "null"
      -          }
      -        ]
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "shortMeaning": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / reducedTo / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / reducedTo / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the computation method, the GET endpoint, and a 5-credit cost with a tier note, which helps an agent budget calls. It stops short of describing response shape or rate limits, so a 4 rather than a 5.

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 core sentence is front-loaded and waste-free, with bracketed metadata (group, endpoint, cost) clearly separated. Slightly denser than necessary, but every line carries information an agent could use.

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 not be explained, and annotations cover safety. However, the description advertises a date query parameter that the input schema does not expose, leaving a real ambiguity about how an agent should request a non-today date — a completeness gap for a tool whose whole point is date-scoped computation.

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 description coverage is 100% for the two declared parameters (fields, precision), so the schema does the heavy lifting and baseline 3 applies. The description does mention a `?date=YYYY-MM-DD` query that is nowhere in the input schema, which adds information but in a form the agent cannot act on through the declared parameters.

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 names a specific verb and resource ('Compute today's personal angel number') and clarifies the method (digit-sum reduced to a single digit), which differentiates it from siblings like astroway_esoteric_angel_numbers_number or *_by_life_path_n. It does not explicitly name those siblings, so it falls short of a 5.

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 word 'today's' and the optional date query imply the intended use case, but there is no explicit statement of when to call this versus astroway_esoteric_angel_numbers or astroway_esoteric_angel_numbers_decode. Usage is only inferable from the name and scope.

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