Skip to main content
Glama

guided_practice

A guided practice for a chakra: meditation, breath, yoga, mudra, mantra, exercise, crystal, food; adapted to deficiency or excess. Price: $0.01 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": {
      "chakra": "<chakra>"
    },
    "name": "guided_practice"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of the core texts (default it)
typeNo
stateNo
chakraYesChakra id or alias
minutesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the paid-per-call nature ('$0.01 USDC per call (x402)'), which is a significant operational trait an agent must know before invoking. However, it says nothing about whether the call has side effects, whether output is deterministic, whether payment must be pre-authorized, or what the response contains.

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?

A single dense sentence front-loads the purpose and modality list, with pricing appended. It is compact and mostly front-loaded, though the semicolon-joined enum dump is largely redundant with the schema and could be trimmed in favor of documenting `minutes` and `lang`.

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 five-parameter generative tool with no annotations and no output schema, the description covers purpose and payment but leaves two parameters and the return shape unspecified. An agent knows roughly what it will get back (a practice text for a chakra) and that it costs money, but not the output format, defaults, or language behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 40%, so the description should compensate. It adds real meaning for `state` ('adapted to deficiency or excess') but only mentions two of the four enum values, omitting 'balanced' and 'unstable'. Repeating the `type` values merely duplicates the schema enum, and neither `lang` (default it) nor `minutes` receives any mention in the description.

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 ('a guided practice for a chakra') and enumerates the eight practice modalities, which map onto the `type` enum, plus the deficiency/excess framing. It is specific enough to distinguish this from sibling chakra tools like chakra_sheet or chakra_list, though it never uses an explicit verb such as 'generate' or 'return'.

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 guidance on when to call this versus alternatives such as chakra_sheet or chakra_checkup_score, and no stated preconditions (e.g. that a chakra identifier must already be known). The 'adapted to deficiency or excess' phrase implies a use case but is not framed as a when-to-use rule, and no exclusions are given.

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