Vayu Breathing

Start a breathing session

start_breathing_session

Read-onlyIdempotent

Show an interactive timer that paces one named breathing technique for calm, focus or sleep. It is a relaxation exercise, not medical treatment. Use it when the user asks for a specific technique now, such as box breathing, 4-7-8, cyclic sighing, extended exhale, a 4-8 slow exhale, humming bee breath or alternate nostril breathing. The user presses Start in the timer. Nothing is saved and no account is needed.

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": {
      "pattern": "<pattern>"
    },
    "name": "start_breathing_session"
  }
}

Input Schema

Name	Required	Description	Default
`minutes`	No	Session length in minutes: 1, 2, 3, 5 or 10. Defaults to 1.
`pattern`	Yes	Which rhythm to pace. box: box breathing, 4-4-4-4, for focus. triangle: 4-7-8 breathing, for winding down to sleep. exhale: extended exhale, 3-2-6-2, to unwind. sigh: cyclic sighing, two inhales then one long exhale (3-1-6), to calm down fast. nadi: alternate nostril breathing (Anulom Vilom), 4-2-4 on each side. coherent: an even 4-2-4-2 rhythm, for steady calm (the rhythm of Vayu's guided pauses). slow_exhale: 4-8 slow exhale with no holds, for a panic moment or lying in bed. hum: humming bee breath (Bhramari), breathe in 4, hum out 6, to quiet a busy mind.

Output Schema

Name	Required	Description	Default
`name`	Yes
`phases`	Yes
`minutes`	Yes
`pattern`	Yes
`subtitle`	Yes
`breathsPerMinute`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the description goes beyond them by disclosing that the timer is interactive (the user presses Start), that nothing is saved, that no account is needed, and that this is a relaxation exercise rather than medical treatment. The safety framing and no-persistence guarantee are genuinely useful additions not derivable from the 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?

Front-loaded with the core action, then usage trigger, then interaction and safety notes in a logical order with no filler. The enumerated technique list is somewhat redundant with the enum descriptions, which keeps it from a 5.

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 two-parameter tool with a complete output schema and full annotation coverage, the description supplies the missing human-facing context: interactivity, no persistence, no auth, and a medical disclaimer. Nothing an agent needs in order to invoke it correctly appears to be missing.

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 enum descriptions already explain each rhythm and its purpose, so the schema does the heavy lifting. The description re-lists technique names that map onto enum values (box, 4-7-8, humming bee breath) but adds no new syntax, defaults or constraints beyond what the schema states.

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 opening sentence names a specific verb and resource ('Show an interactive timer that paces one named breathing technique') and scopes it to calm, focus or sleep. It is clearly distinct from a planning or lookup tool, though it never names a sibling like build_breathing_plan or explain_breathing_technique to make the boundary explicit.

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?

It states a clear trigger condition: use when the user asks for a specific technique now, and enumerates concrete examples (box breathing, 4-7-8, cyclic sighing, and so on). The word 'now' implicitly separates it from planning-oriented siblings, but no explicit exclusion or named alternative is given.

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?