Skip to main content
Glama

AstroWay Core astrology

Algol Minimum

astroway_calendar_algol_minimum
Read-onlyIdempotent

Find the nearest minimum brightness moment of Algol (Beta Persei), the eclipsing variable star, within a date range.

[Group: Calendar & Cycles] [Endpoint: POST /v1/algol-minimum] [Required: startDate, endDate] [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": {
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "astroway_calendar_algol_minimum"
  }
}

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.
endDateYes
longitudeNo
precisionNoCompact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.
startDateYes

Output Schema

NameRequiredDescriptionDefault
countNo
minimaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / properties / longitude / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / longitude / 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 / minima / anyOf
      Previous value: -[
      -  {
      -    "items": {
      -      "anyOf": [
      -        {
      -          "additionalProperties": {},
      -          "properties": {
      -            "date": {
      -              "anyOf": [
      -                {
      -                  "type": "string"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "isNighttime": {
      -              "anyOf": [
      -                {
      -                  "type": "boolean"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            },
      -            "jd": {
      -              "anyOf": [
      -                {
      -                  "type": "number"
      -                },
      -                {
      -                  "type": "null"
      -                }
      -              ]
      -            }
      -          },
      -          "type": "object"
      -        },
      -        {
      -          "type": "null"
      -        }
      -      ]
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "items": {
      +      "anyOf": [
      +        {
      +          "additionalProperties": {},
      +          "properties": {
      +            "date": {
      +              "type": [
      +                "string",
      +                "null"
      +              ]
      +            },
      +            "isNighttime": {
      +              "type": [
      +                "boolean",
      +                "null"
      +              ]
      +            },
      +            "jd": {
      +              "type": [
      +                "number",
      +                "null"
      +              ]
      +            }
      +          },
      +          "type": "object"
      +        },
      +        {
      +          "type": "null"
      +        }
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description usefully adds pricing ('10 credits, Tier 1') and the endpoint/group, which annotations do not cover. What it omits is meaningful behavior: whether one minimum or a list of minima in the range is returned, and what happens when no minimum falls inside the supplied range.

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?

One descriptive sentence followed by compact bracketed metadata for group, endpoint, required params, and cost. It is front-loaded and free of filler; the required-params line is mild redundancy with the schema but costs little.

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 documented here, and the cost/endpoint metadata is helpful. Still, for a tool whose only distinguishing feature is its relationship to a similarly named sibling, the definition leaves the routing question and the undisclosed 'longitude' parameter unresolved.

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 40%, and the description compensates only by restating that startDate and endDate are required, which the schema already declares. The bare 'longitude' parameter (number or null) is left completely unexplained in both schema and description, and no date-range limits or inclusive/exclusive semantics are given.

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 gives a specific verb and resource ('find the nearest minimum brightness moment of Algol') and even glosses the object as 'Beta Persei, the eclipsing variable star', which is genuinely informative. It does not, however, distinguish this tool from its near-identically scoped sibling astroway_calendar_algol_minimum_nearest, and the word 'nearest' in this description muddies rather than clarifies which of the two an agent should pick.

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. The presence of astroway_calendar_algol_minimum_nearest in the sibling list makes routing genuinely ambiguous, and the description offers no rule for choosing between them. It states only a date-range constraint, which is a scope fact rather than 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