Skip to main content
Glama

chakra_list

List of the 7 chakras with a short summary (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_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/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 mostly doesn't: it never states idempotency, side effects, or response structure beyond 'short summary'. The repeated '(free)' hints at a pricing/entitlement tier but is never explained, leaving the agent unsure whether access can fail.

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?

Very short and front-loaded, but the parenthetical '(free)' followed by a trailing 'Free.' is a duplicated fragment that wastes a full sentence. Trimming it would leave a single clean, informative clause.

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?

For a simple read-only reference list with complete schema coverage and no output schema, the description is barely sufficient: it conveys what comes back but not the language parameter's effect or any access constraints. An agent can call it correctly, but with little confidence about the response.

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?

Only one optional parameter (lang) exists and the schema documents it fully with an enum and default, so the schema does the heavy lifting. The description adds nothing about language behavior, which is acceptable at 100% coverage but earns no credit.

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 resource and return shape: the 7 chakras with a short summary, so an agent knows it is a static reference list rather than a lookup by date or id. It does not distinguish itself from siblings like chakra_sheet or chakra_of_the_day, which offer chakra data in other forms.

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?

No when-to-use guidance, no prerequisites, and no pointer to alternatives such as chakra_sheet or chakra_checkup_questions. The agent must infer from the name alone when this list is the right call.

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