Skip to main content
Glama

biorhythm_compatibility

Traditional biorhythm compatibility of two people (0-100% per cycle and overall). 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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "biorhythm_compatibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYesBirth date of person A
bYesBirth date of person B
langNoLanguage of the core texts (default it)

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?

No annotations are supplied, so the description carries the full burden — and it does disclose two non-obvious traits: the per-call cost and payment mechanism ($0.01 USDC via x402) and the shape of the result (per-cycle plus overall percentages). What it omits is whether dates must be in a specific format, which cycles are covered, or how invalid input is handled.

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 with no filler: the core function and result format come first, with the pricing constraint appended. Nothing is repeated from the schema or title, and every clause carries information.

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?

For a three-parameter, side-effect-free computation with no output schema, the description covers what is returned and the payment requirement. It could be stronger by naming the cycles evaluated or clarifying how lang affects the returned texts, but an agent has enough to call it correctly.

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 all three parameters are already documented, including the lang enum and its default. The description confirms that a and b are the two people being compared but adds nothing about date formatting or what lang actually changes in the output, so the 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 names a specific verb-and-resource pair (biorhythm compatibility between two people) and states the output scale (0-100% per cycle and overall), which is enough to separate it from siblings like biorhythm_day or biorhythm_range. It stops short of explicitly contrasting itself with those siblings, so it lands just below the top score.

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 phrase 'of two people' implies the use case (comparing two birth dates) but the description never states when to prefer this over biorhythm_day, biorhythm_range, or biorhythm_reading. There are no exclusions, prerequisites, or alternative-routing guidance, so usage must be inferred.

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