Skip to main content
Glama

chakra_of_the_day

Today's biorhythms mapped to the chakra to work on, with why, affirmation, stone and a short breathing practice. Exclusive BioRitmo x BioAura combination. 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": "chakra_of_the_day"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDay (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

B3.2/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 does disclose two things annotations would not: the exact output payload composition and a per-call price of $0.02 USDC via x402, which is important cost/payment context. It says nothing about latency, rate limits, failure modes, or what happens when birth data is inconsistent, so coverage is partial rather than rich.

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?

Three short sentences, front-loaded with the payload description before the pricing note. The 'Exclusive BioRitmo x BioAura combination' clause is marketing filler that does not help an agent decide or invoke, costing a perfect score.

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?

There is no output schema, and the description partially compensates by enumerating the returned elements (why, affirmation, stone, breathing practice), which is genuinely useful. It still omits return shape/structure, localization behavior, and any indication of whether the reading is deterministic for a given birth date. Adequate but with clear gaps for a paid, three-parameter 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 description coverage is 100%, so birth, date and lang are already documented with formats, defaults and an enum. The description adds only an indirect hint ('Today's') that ties to the date default and says nothing about how lang changes the 'core texts'. Baseline 3 applies when the schema does the heavy lifting.

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 concrete deliverable: today's biorhythms mapped to a chakra, bundled with 'why, affirmation, stone and a short breathing practice'. That is far more specific than a restated title. It does not, however, distinguish itself from siblings such as biorhythm_day or chakra_list, so an agent must infer the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative among the many chakra/biorhythm siblings. The only implicit signal is 'Today's', which scopes it to a daily reading rather than a date-range or checkup tool. An agent gets no help choosing between this and biorhythm_day.

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