Skip to main content
Glama

AstroWay Applied readings

Moon-Phase Sleep Tips

astroway_wellness_sleep_cycles
Read-onlyIdempotent

Sleep recommendations per moon phase. Pair with /sun-times to find current phase.

[Group: Wellness] [Endpoint: POST /v1/wellness/sleep-cycles] [Required: date] [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": {
      "date": "<date>"
    },
    "name": "astroway_wellness_sleep_cycles"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
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
noteNo
disclaimerNo
moonPhaseTipsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedOutput schema / properties / date / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / disclaimer / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / disclaimer / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / moonPhaseTips / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "phase": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "tip": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "phase": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "tip": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / note / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / note / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already establish readOnly/idempotent/non-destructive, so the description only needs to add context. It does add cost ('10 credits, Tier 1'), the endpoint, and the required-parameter note, which is genuinely useful. It says nothing about what the recommendations look like or whether results are cached per date, but the output schema covers the return shape.

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 the capability, followed by a compact bracketed metadata block. The bracket lines are slightly noisy but each carries distinct facts (group, endpoint, required param, cost) rather than filler.

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?

This is a simple single-required-param read tool with an output schema, so the description doesn't need to explain return values. It is still incomplete on the one thing that matters: the meaning and timezone of 'date', plus a dangling '/sun-times' reference instead of an actual tool name.

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 coverage is 67%; the two documented params (fields, precision) are explained only in the schema, while 'date' — the sole required parameter — has no schema description and is only restated as 'Required: date'. The description never clarifies whether date is the night of the tips, a birth date, or a local vs UTC calendar day, which is the ambiguity an agent most needs resolved.

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 concrete resource and output — 'sleep recommendations per moon phase' — which separates it from wellness siblings like astroway_wellness_diet or astroway_wellness_cycle. It stops short of an explicit verb (returns/generates) and doesn't say whether the recommendations are keyed to a birth chart or just the calendar date.

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?

One real workflow hint is given: find the current phase first via '/sun-times'. That points at a prerequisite, but the referenced path is not a resolvable sibling tool name (the actual tool is astroway_western_sun_times), and there is no guidance on when to prefer this over astroway_calendar_moon_phase or astroway_render_moon_phase.

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