Skip to main content
Glama

chakra_checkup_questions

Chakra check-up questions (quick 14 or full 28), different every time (free). Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chakra_checkup_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)
modeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the full behavioral burden. It usefully discloses non-determinism ("different every time") but says nothing about return shape, whether answers can be cached or re-fetched, or how the questions relate to scoring; "(free). Free." is cost marketing, not behavioral context an agent needs to invoke correctly.

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

Conciseness3/5

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

One short sentence that front-loads the core fact, which is good, but the claim "free" is stated twice — once parenthetically and once as a dangling sentence — and neither instance earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter tool with no output schema, the description should say what actually comes back (a list of question texts? keyed items?) and how it feeds the scoring tool. Neither is covered, and the non-determinism note raises a practical question — whether repeated calls yield usable, matchable question sets — that goes unanswered.

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 50%: lang already documents itself and its default, while mode has no schema description. The description partially compensates by explaining mode's meaning in terms of question count (14 vs 28), which is genuinely added value beyond the enum values.

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 resource — check-up questions — and quantifies both variants (14 quick, 28 full), which lets an agent tell it apart from chakra_checkup_score. It stops short of an explicit verb ("get"/"retrieve") or a direct contrast with the scoring sibling, so it is clear but not fully differentiated.

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 statement of when to call this versus chakra_checkup_score or chakra_sheet, and no hint that these questions are presumably the input to the scoring tool. The only selection signal is the quick/full distinction, which is handled by the mode parameter rather than by guidance.

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