Skip to main content
Glama

biorhythm_range

Biorhythm series for up to 366 days with all critical days. Price: $0.02 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_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days (default 30)
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?

With no annotations, the description carries the full burden; it usefully discloses the per-call price and x402 payment model, plus the inclusion of critical days. It does not explain payment/auth mechanics, rate limits, response structure, or what happens at the 366-day boundary, and the stated 366-day cap conflicts with the schema's much larger numeric maximum.

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 definition is two sentences, front-loads the tool's purpose, and follows with the pricing detail without redundant wording. Every sentence contributes useful information.

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?

The description is adequate for a four-parameter, paid series-generation tool whose parameters are fully documented in the schema. However, with no output schema and no annotations, it should say more about the returned series format and payment/authentication flow.

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%, so the parameter semantics baseline is 3. The description adds only the practical 366-day cap, but that cap is not reflected in the schema's maximum and no other parameter meaning is expanded.

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 clearly identifies the resource as a biorhythm series and scopes it to a multi-day range of up to 366 days, including critical days. It is understandable without the schema, but it does not explicitly distinguish itself from siblings such as biorhythm_day or biorhythm_critical_days.

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?

The 'up to 366 days' framing implies this is for multi-day series rather than a single-day reading, which provides minimal usage context. However, it names no alternatives, exclusions, or conditions that would tell an agent when to choose this over biorhythm_day or biorhythm_critical_days.

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