Skip to main content
Glama

chakra_checkup_score

Scores check-up answers: balance of the 7 chakras (deficiency/excess), priorities, goals and where to start. 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": {
      "answers": "<answers>"
    },
    "name": "chakra_checkup_score"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)
answersYesMap question id -> answer 0..3 (from /v1/checkup/questions)

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?

No annotations are supplied, so the description carries the full burden, and it does disclose the most consequential trait: each call costs $0.02 USDC via x402, which the agent must know before invoking. It also enumerates the outputs the computation produces. It stops short of describing validation behavior (e.g., what happens with out-of-range or missing answer ids) or whether results are deterministic/persisted.

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?

Two compact sentences: the first front-loads what is computed and what is returned, the second carries the pricing constraint. No filler or repetition. Slightly over-compressed in that the returned-fields list is a comma chain rather than a clear output summary.

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, and the description compensates by naming the result components (balance per chakra, deficiency/excess, priorities, goals, starting point). The paid-call model is stated, which matters for a tool with no annotations. Missing only edge-case behavior and the prerequisite relationship to the questions endpoint.

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%, with the answers map, the 0..3 range and the lang enum all documented in the schema itself. The description adds nothing about parameter meaning beyond what the schema says, 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?

States a specific verb and resource: it scores check-up answers and returns chakra balance (deficiency/excess), priorities, goals and a starting point. That is far more than a restatement of the name. It does not name the obvious companion tool chakra_checkup_questions, so sibling differentiation is only implied by the input reference to a questions endpoint.

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?

Usage is implied: it operates on 'check-up answers', and the schema points at /v1/checkup/questions as the source of those answers, so an agent can infer a questions-first flow. There is no explicit when-to-use vs when-not guidance, no statement about whether all questions must be answered, and no named alternative for reading the raw 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