Skip to main content
Glama
astroway

astroway-mcp

Official

Biorhythm (SVG)

render_biorhythm
Read-onlyIdempotent

Generate a sine plot of physical, emotional, and intellectual biorhythm cycles based on birth date and date range. Visualize daily fluctuations to assess personal energy patterns.

Instructions

Three-curve sine plot of physical (23d), emotional (28d), and intellectual (33d) cycles since birth.

[Group: Visualization]

Example request body: {"birthDate":"1990-05-15","rangeStart":"2026-01-01","rangeEnd":"2026-12-31","options":{"width":1000,"height":400}}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birthDateYes
rangeStartYes
rangeEndYes
optionsNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating no destructive effects. The description adds that the output is an SVG plot (from title) and includes an example request, but does not detail edge cases or further behavioral traits. It complements annotations well without contradicting them.

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 description is concise with two sentences and an example, front-loading the key purpose. The group marker adds minimal value. Could be slightly more efficient, but overall well-structured.

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?

Despite having 4 parameters (including a nested options object), the description does not explain output format, parameter meanings, or return value. The example partially compensates, but the tool requires richer context for correct invocation, especially given the complexity of options.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no explanations for parameters like birthDate, rangeStart, rangeEnd, or the options object. The example request body hints at usage but does not define semantics, leaving the agent to infer meaning solely from the schema.

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

Purpose5/5

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

The description clearly states it renders a 'Three-curve sine plot of physical, emotional, and intellectual cycles since birth,' providing a specific verb and resource. Among many sibling render tools, this uniquely identifies biorhythm generation.

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 guidance on when to use this tool versus alternatives (e.g., other render tools). It does not specify prerequisites, limitations, or scenarios where it is or isn't appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/astroway/astroway-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server