AstroWay Astrology API (full catalogue)

Algol Nearest Minimum

astroway_calendar_algol_minimum_nearest

Read-onlyIdempotent

Find the single nearest Algol brightness minimum before or after a given date.

[Group: Calendar & Cycles] [Endpoint: POST /v1/algol-minimum/nearest] [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_calendar_algol_minimum_nearest"
  }
}

Input Schema

Name	Required	Description
`date`	Yes
`fields`	No	Compact mode: comma-separated dotted paths to keep, relative to `data`, e.g. "planets.name,planets.longitude,houses.cusp". Omit for the whole response.
`longitude`	No
`precision`	No	Compact mode: round fractional numbers to this many decimals. Longitudes carry 14 by default; 2 is finer than any chart is drawn.

Output Schema

Name	Required	Description	Default
`jd`	No
`date`	No
`time`	No
`hoursUntil`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 7, 2026

removedInput schema / properties / longitude / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / longitude / 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"
+]
```

removedOutput schema / properties / hoursUntil / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / hoursUntil / type
```
Added value: +[
+  "number",
+  "null"
+]
```

removedOutput schema / properties / jd / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / jd / type

Added value: +[
+  "number",
+  "null"
+]

removedOutput schema / properties / time / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / time / type
```
Added value: +[
+  "string",
+  "null"
+]
```

First observedOct 5, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety behavior is covered. The description contributes useful operational context (POST /v1/algol-minimum/nearest, required `date`, 10 credits Tier 1 cost), but says nothing about how 'nearest' is resolved across the date boundary or what the result includes.

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 wastes no words. The bracketed metadata block (group, endpoint, required, cost) is compact and scannable, though it consumes roughly half the description with mostly infrastructural rather than semantic information.

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-value explanation is not required, and the single-purpose lookup nature keeps the description broadly adequate. Still missing is any explanation of the `longitude` parameter and any routing hint against the sibling algol_minimum tool, which are the two things an agent is most likely to get wrong.

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 50%, and the description compensates for none of the gap: `longitude` is completely undocumented in both schema and description, and `date` is described only as 'Required' with no format or timezone note. Only `fields` and `precision` are self-documented in the schema, leaving the unexplained `longitude` parameter a real ambiguity for a tool about bright-star minima.

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 single nearest Algol brightness minimum') with an explicit scope ('before or after a given date'), which separates it from the likely list/range sibling astroway_calendar_algol_minimum. It stops short of naming that sibling, so the differentiation is implicit rather than stated.

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 and no reference to the alternative astroway_calendar_algol_minimum tool, which an agent would plausibly confuse with this one. The phrase 'before or after a given date' implies a nearest-match lookup but leaves the tie-breaking / direction semantics unstated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All AstroWay Astrology API (full catalogue) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?