Skip to main content
Glama

biorhythm_critical_days

Upcoming critical (phase change) days of each cycle, for reminders. Price: $0.005 USDC per call (x402).

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": {
      "birth": "<birth>"
    },
    "name": "biorhythm_critical_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow length (default 60)
fromNoFirst day (default: today UTC)
langNoLanguage of the core texts (default it)
birthYesBirth date YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it does disclose the paid x402 pricing ($0.005 USDC per call), which is valuable behavioral context. However, it says nothing about read-only nature, whether payment failure blocks the call, or what the returned structure looks like.

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 short sentences: purpose first, cost second. No filler, no redundancy, and the key noun phrase leads.

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?

Adequate for a four-parameter read tool with a fully described schema and no output schema, but the description never characterizes the return payload (one entry per cycle? dates plus labels?) or the payment flow, which are the main unknowns for an agent invoking it.

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 100%, with documented defaults for days (60), from (today UTC), and lang (it), plus the required birth format. The description adds no parameter meaning beyond the schema, so the baseline of 3 applies.

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?

Names a specific resource — the upcoming critical (phase-change) days of each biorhythm cycle — with parenthetical clarification of what 'critical' means. It is distinguishable from siblings like biorhythm_best_days or biorhythm_day, though no sibling is 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 Guidelines3/5

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

'for reminders' implies a use case, and 'upcoming' implies a forward-looking window, but the description gives no explicit when-to-use vs when-not guidance and does not point to biorhythm_range or biorhythm_day for alternative views.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources