AstroWay Applied readings

Biorhythm Best Days

astroway_wellness_biorhythm_best_days

Read-onlyIdempotent

The highest-scoring days in a range (up to 366 days): score = 100 x (sum of the three cycle values + 3) / 6, critical days left out by default. A historical model, not a prediction and not health advice; the disclaimer travels with the answer.

[Group: Wellness] [Endpoint: POST /v1/wellness/biorhythm/best-days] [Required: birthDate] [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": {
      "birthDate": "<birthDate>"
    },
    "name": "astroway_wellness_biorhythm_best_days"
  }
}

Input Schema

Name	Required	Description
`count`	No	How many days to return, best first.
`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.
`rangeEnd`	No
`birthDate`	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.
`rangeStart`	No
`excludeCritical`	No	Leave out days on which any cycle crosses zero.

Output Schema

Name	Required	Description	Default
`range`	No
`formula`	No
`bestDays`	No
`birthDate`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real substance on top: the scoring formula, the default exclusion of zero-crossing days, and the fact that the disclaimer is carried in the response. It also sets expectations that this is a historical model rather than a prediction.

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 dense sentences with the scope and formula front-loaded and no filler. The bracketed metadata block (group, endpoint, required, cost) is compact and useful rather than padding.

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?

Output schema exists, so return shape need not be described, and cost/endpoint/required params are disclosed. The gap is what happens when the optional range bound dates are omitted, and how returned days relate to the requested range.

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 57%, and the description adds the 366-day span cap and confirms the excludeCritical default, both useful beyond the schema. However, rangeStart/rangeEnd are undocumented in both places, and it does not explain the interaction between count and the range window.

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?

States a specific resource and verb: the highest-scoring days within a range, up to 366 days, with the exact scoring formula. It is distinguishable from astroway_wellness_biorhythm (single-date cycles) by the ranking/range framing, though the sibling is never named explicitly.

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?

No when-to-use or when-not guidance, and no pointer to the related sibling tools such as astroway_wellness_biorhythm or astroway_render_biorhythm. The 'not health advice' disclaimer is a caution, not selection guidance.

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

All AstroWay Applied readings 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?