Skip to main content
Glama
tresor4k

macalc

calculate_biorhythm

Compute your physical, emotional, and intellectual biorhythm cycles for any date. Enter birth date and target date to receive cycle values and zone.

Instructions

Compute physical, emotional, and intellectual biorhythm cycles for a date based on birth date. Use for self-tracking enthusiasts (pseudoscience). Inputs: birth date, target date. Returns 3 cycle values (-100 to +100) and zone. See list_bundles for related 'fun' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
birth_dateYesBirth date YYYY-MM-DD
target_dateYesTarget date YYYY-MM-DD

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior4/5

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

Without annotations, the description explains the tool computes cycles and returns three values (-100 to +100) and a zone. It is a read-only calculation with no destructive behavior, and the disclosure is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two sentences, front-loading the purpose and including key details without unnecessary words.

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

Completeness4/5

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

The description covers input, output format, and purpose. Given the simple nature of the tool and presence of an output schema, it is mostly complete, though edge cases like timezone or invalid dates are not addressed.

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?

The input schema has 100% coverage for two parameters, both described as 'YYYY-MM-DD' strings. The description only reiterates the parameter names without adding new meaning, so baseline score is appropriate.

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 the tool computes physical, emotional, and intellectual biorhythm cycles for a date based on birth date. It also specifies the target audience (self-tracking enthusiasts) and distinguishes from siblings by referencing list_bundles for related fun calculators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context for use (self-tracking, pseudoscience) and directs to list_bundles for similar tools, but does not explicitly state when not to use or compare with specific alternatives.

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/tresor4k/macalc-mcp'

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