Skip to main content
Glama

biorhythm_day

Biorhythm values for one day: physical, emotional, intellectual and adept cycles (-100..+100), trend and critical days. 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_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay to read (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.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden, and it does disclose two non-obvious traits: the scale of returned values (-100..+100) and the paid model ($0.005 USDC per call via x402). It does not cover failure modes or defaults, but for a read-only computed lookup the pricing and output range are the material facts.

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 tight sentences with zero filler: the output content comes first, the payment terms last. Every clause carries information an agent needs.

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?

There is no output schema, but the description compensates by naming the returned values and their range. Combined with a fully described three-parameter schema, an agent has enough to call this correctly; only error/empty-day behavior is unstated.

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 coverage is 100%, so 'birth', 'date' and 'lang' are already documented with descriptions and an enum. The description adds only the implicit single-day scope, which the 'date' parameter description already states, so baseline 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?

The description uses a specific resource ('Biorhythm values') scoped to a single day, and enumerates what is returned: physical, emotional, intellectual and adept cycles, trend and critical days. That makes it clearly distinguishable from a range or multi-day variant, though it does not name any sibling 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?

Usage is only implied by the 'for one day' framing, which suggests this is the single-day read rather than a range or best-days lookup. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative tool.

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