Vayu Breathing

Explain a breathing technique

explain_breathing_technique

Read-onlyIdempotent

Explain a named breathing technique the way Vayu teaches it: what it is, step-by-step instructions, the best time of day, cautions, and which timer pattern paces it, if any. Use it when the user asks what a technique is or how to do it, including pranayama such as Bhramari, Ujjayi, Nadi Shodhana, Kapalabhati or Bhastrika. Forceful techniques are explained with their cautions but are not paced by the timer. Text only; no timer is shown.

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": {
      "technique": "<technique>"
    },
    "name": "explain_breathing_technique"
  }
}

Input Schema

Name	Required	Description	Default
`technique`	Yes	Which technique. box: Box breathing (Sama Vritti, square breathing). four_seven_eight: 4-7-8 breathing (relaxing breath). cyclic_sighing: Cyclic sighing (physiological sigh). extended_exhale: Extended exhale. slow_exhale: 4-8 slow exhale. steady_rhythm: Steady 4-2-4-2 rhythm. alternate_nostril: Alternate nostril breathing (Nadi Shodhana, Anulom Vilom). humming_bee: Humming bee breath (Bhramari). ocean_breath: Ocean breath (Ujjayi). three_part: Three-part breath (Dirga Svasa). diaphragmatic: Diaphragmatic breathing (abdominal breathing). cooling_breath: Cooling breath (Sitali, Sitkari). left_nostril: Left-nostril breathing (Chandra Bhedana). right_nostril: Right-nostril breathing (Surya Bhedana). kapalabhati: Skull shining breath (Kapalabhati). bhastrika: Bellows breath (Bhastrika).

Output Schema

Name	Required	Description	Default
`name`	Yes
`steps`	Yes
`timer`	Yes
`caution`	Yes
`bestTime`	Yes
`category`	Yes
`evidence`	No
`whatItIs`	Yes
`technique`	Yes
`alsoCalled`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the burden is low. The description still adds useful behavioral context beyond them: no timer is launched, and forceful techniques (Kapalabhati, Bhastrika) are explained with cautions but deliberately not paced by the timer — a non-obvious rule the agent could not derive from annotations.

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?

Three tight sentences, front-loaded with the output contract before the usage trigger. Minor redundancy in stating the 'no timer' fact twice ('which timer pattern paces it, if any' and 'Text only; no timer is shown'), though the repetition reinforces a key distinction.

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

Completeness5/5

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

Complexity is low (one enum parameter, output schema present), and the description covers what the tool does, when to call it, what it returns conceptually, and the one edge case (forceful techniques). Nothing needed to invoke it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100% and every enum value already carries a gloss, so the baseline is 3. The description goes slightly beyond by tying specific enum values (forceful techniques) to a behavioral outcome — explained but un-paced — which is meaning the schema does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource ('Explain a named breathing technique') followed by an explicit enumeration of what the explanation contains: definition, step-by-step instructions, best time of day, cautions, and timer pattern. The closing line ('Text only; no timer is shown') separates it from the session-starting siblings without needing to name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear trigger: 'Use it when the user asks what a technique is or how to do it,' and lists pranayama examples so the agent knows the question domain. It does not explicitly name alternatives such as start_breathing_session for when the user actually wants to practice, so the exclusion is implied by 'text only' rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vayu Breathing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?