Skip to main content
Glama

biorhythm_best_days

Best days in the next 1-90 days for an activity (sport, study, exam, social, creative, decisions, meditation, rest), skipping critical days. Ideal for calendar and planning agents. 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>",
      "activity": "<activity>"
    },
    "name": "biorhythm_best_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow length (default 30)
fromNoFirst day (default: today UTC)
langNoLanguage of the core texts (default it)
birthYesBirth date YYYY-MM-DD
limitNoHow many days to return (default 5)
activityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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, and it does disclose two real traits: the 90-day cap on the search window and the $0.02 USDC per-call charge via x402. It says nothing about return shape (how many days, format) or what happens on out-of-range requests, so behavioral coverage is partial for a paid read tool.

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 plus a price clause, with the core capability and the critical-day exclusion front-loaded and the commercial term last. Every phrase carries information; nothing is padding.

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?

For a 6-parameter paid tool with no annotations and no output schema, the description covers purpose and cost but leaves the return contract and the interaction of days/limit ambiguous. It is adequate to select the tool but not to fully predict its behavior.

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 coverage is already 83%, so the baseline is 3; the description earns an extra point by supplying the 1-90 cap on the window length, a constraint absent from the schema's integer bounds, and by listing the activity domain. It adds nothing for from, lang, or limit beyond the schema.

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 gives a specific verb+resource: returns the best days within a 1-90 day window for a named activity, skipping critical days. That scope and the critical-day exclusion implicitly separate it from biorhythm_day, biorhythm_range and biorhythm_critical_days, though no sibling is named outright.

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?

"Ideal for calendar and planning agents" gives a usage context, but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as biorhythm_range or biorhythm_critical_days for overlapping date-window questions.

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