AstroWay Astrology API (full catalogue)

MCP Multi-Agent Coordinate

astroway_mcp_multi_agent_coordinate

Read-onlyIdempotent

Run N personas in parallel + LLM synthesis.

[Group: MCP Advanced] [Endpoint: POST /v1/mcp/multi-agent-coordinate] [Required: question, agents] [Cost: 100 credits (Tier 4)]

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": {
      "question": "<question>",
      "agents": "<agents>"
    },
    "name": "astroway_mcp_multi_agent_coordinate"
  }
}

Input Schema

Name	Required	Description	Default
`chart`	No	Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as "Placidus" is refused, and the case matters because I and i are two different Sunshine systems.
`agents`	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.
`language`	No		en
`question`	Yes
`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
`synthesis`	No
`individual`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 7, 2026
- removedInput schema / properties / chart / properties / ayanamsaId / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedInput schema / properties / chart / properties / ayanamsaId / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / synthesis / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / synthesis / type
```
Added value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedNov 6, 2026

changedInput schema / properties / chart / description

Previous value: -"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single Swiss Ephemeris letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."New value: +"Birth data for a single natal chart. Required: date (YYYY-MM-DD), time (HH:mm:ss), latitude and longitude in decimal degrees. The short forms lat, lon, lng and tz are rejected with 400 INVALID_FIELD; pass the full names. timezoneOffset is hours from UTC and defaults to 0, meaning UTC; send timezone instead (an IANA name such as Europe/Kyiv, or auto) and the offset for that date is worked out, summer time included. city is a display label only: nothing here geocodes it, so it never stands in for coordinates. houseSystem is a single house-system letter, P by default; a name such as \"Placidus\" is refused, and the case matters because I and i are two different Sunshine systems."

First observedOct 5, 2026

TDQS

C2.7/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 earns credit for disclosing the cost (100 credits, Tier 4) and that execution is parallel with an LLM synthesis step, which materially affects latency and spend expectations. It still says nothing about failure handling, whether synthesis is deterministic, or what the response actually contains (the largest gap for a billed LLM-backed call).

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 prose is a single front-loaded sentence with the mechanism stated first, and the bracketed metadata lines are compact and scannable. Nothing is padded or repeated. The efficiency is somewhat bought by under-specification, which is penalized elsewhere rather than here.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex, billed orchestration tool with six parameters, a nested chart object, an enum-constrained agent list and an output schema, yet the description is one clause plus metadata. An agent cannot tell from the definition what persona names to supply, whether the chart is mandatory in practice, or how cost scales with agent count. Presence of an output schema removes the need to describe return values, but the input-side opacity leaves it under-specified for its complexity.

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 50%, and the description contributes only "Required: question, agents" — information the schema's required array already carries. Critically, it never explains what valid values for `agents` look like (persona identifiers? free-text role names? how the 2-4 limit interacts with synthesis quality) or why a `chart` would accompany the question. The nested chart object is documented in the schema, but the tool's own two core parameters add no meaning beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The one-line description names a verb and a mechanism ("Run N personas in parallel + LLM synthesis"), so the agent knows it is an orchestration/aggregation tool rather than a single calculation. However, it never says what the personas are about (astrological interpretation of the supplied chart) or what the synthesis produces. It also fails to distinguish itself from the sibling astroway_mcp_agent_debate, which plausibly does a very similar multi-persona job.

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 statement of when to pick this over astroway_mcp_agent_debate, astroway_mcp_ai_comparison_coach, or astroway_mcp_ai_chat, no prerequisites, and no note on how many agents are sensible. The only routing information is the bracket metadata listing required fields and cost, which is not usage guidance.

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?