mcp-biorhythm

Overview Schema Source Related Servers Discussions Admin

Get Biorhythm

get_biorhythm

Calculate physical, emotional, and intellectual biorhythm values from a birth date and generate a PNG chart with sine curves for a specified date range.

Instructions

생년월일을 받아 신체(23)·감성(28)·지성(33) 바이오리듬 수치와 사인파 차트 PNG를 반환한다. 날짜 계산은 UTC 자정 기준(타임존 비의존).

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": "get_biorhythm"
  }
}

Input Schema

Name	Required	Description
`birthDate`	Yes	생년월일 (YYYY-MM-DD)
`targetDate`	No	기준일 (YYYY-MM-DD). 생략 시 오늘(UTC).
`rangeDays`	No	기준일 전후 표시 일수

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 19, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, description carries full burden. It discloses that date calculation is UTC midnight (timezone independent), which is a key behavioral detail. However, it does not mention return format specifics, error conditions, or authentication needs.

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?

Two sentences with no redundant information. First sentence defines purpose and output, second clarifies a critical behavioral detail. Every word is functional.

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?

Given no output schema, the description could specify how values and chart are returned (e.g., JSON with base64 PNG). However, for a straightforward biorhythm tool, the description is largely complete. Missing output format details slightly reduce completeness.

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

Parameters4/5

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

Schema provides 100% coverage with descriptions for all three parameters. Description adds value by specifying the cycle periods (23,28,33), which are not in the schema. This enhances understanding beyond 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?

Description clearly states the tool receives a birthdate and returns biorhythm values for physical (23), emotional (28), and intellectual (33) cycles along with a sine wave chart PNG. It specifies the exact resource and action, distinguishing it from any potential siblings.

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?

Description implicitly conveys usage (computing biorhythms) and includes constraints like date calculation at UTC midnight. No explicit when-not-to-use or alternatives, but no sibling tools exist to differentiate from.

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

Deploy Server

Other Tools

get_biorhythmA