Skip to main content
Glama

chakra_sheet

Complete chakra sheet: location, element, body, signals of deficiency and excess, goals, stones, yoga, mudra, mantra, exercise. Price: $0.005 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": {
      "id": "<id>"
    },
    "name": "chakra_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesChakra id (muladhara, svadhisthana, manipura, anahata, vishuddha, ajna, sahasrara) or alias (root, heart, crown...)
langNoLanguage of the core texts (default it)

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?

No annotations exist, so the description carries the full burden. It does usefully disclose the payment model ('$0.005 USDC per call (x402)'), which an agent must know before invoking, but says nothing about error behavior for an invalid chakra id, rate limits, or authentication requirements.

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 short sentences, front-loaded with the resource and its returned fields, then the price. The field enumeration is long but functional; nothing is wasted.

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 simple two-parameter lookup with no output schema, the enumeration of returned content effectively substitutes for return-value documentation, and the price disclosure covers the cost dimension. The missing usage guidance keeps it from a 5.

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%, and the schema already documents both the id pattern/aliases and the lang enum. The description adds no parameter-level meaning beyond the schema, so 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 the resource ('Complete chakra sheet') and enumerates the exact content returned (location, element, body, signals, goals, stones, yoga, mudra, mantra, exercise), which clearly distinguishes it from a list-style sibling like chakra_list. It lacks an explicit verb and never names an alternative tool, but an agent can tell what it retrieves.

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 when-to-use guidance, no alternatives (e.g., chakra_list to discover valid IDs, stone_sheet for stone details), and no prerequisites. Usage is only implied by the noun phrase 'chakra sheet'.

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