Skip to main content
Glama

biorhythm_reading

Full daily reading ready to show a user: values plus the BioRitmo app phrase and practical tip for each cycle (Italian), with linked chakras. Price: $0.01 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_reading"
  }
}

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.7/5.0
Behavior4/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 the two traits an agent most needs: the monetary cost ($0.01 USDC per call via x402) and the composition of the response (values + phrase + tip per cycle + chakras). It stops short of describing the payment handshake, failure modes, or whether the call is idempotent/side-effect free.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence pairing what the agent gets with what it costs — exactly the two things an agent needs before calling a paid tool. The stacked parentheticals make it denser than necessary, but no sentence is wasted.

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, so the description must convey return content, and it does so at a useful level (values, phrase, tip, chakras). Combined with full schema coverage for the three inputs, only the x402 payment flow and error behavior remain undocumented — acceptable for a simple three-parameter read tool.

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, date, and language are already documented, and the baseline of 3 applies. The description adds only partial meaning — it stresses Italian output, which slightly undercuts the schema's it/en enum and per-parameter default semantics rather than enriching them.

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 (a full daily biorhythm reading) and enumerates its contents: cycle values, the BioRitmo app phrase and practical tip, plus linked chakras. It is clearly a richer, presentation-ready variant of a plain values call, but it never names a sibling (e.g. biorhythm_day) to make the boundary explicit.

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?

"Ready to show a user" implies this is the display-oriented choice rather than the raw-data tools, and the mention of a per-call price hints at a deliberate, costed invocation. However, there is no explicit when-to-use/when-not statement and no named alternative for agents that only need numeric values.

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