Vayu Breathing

Build a 7-day breathing plan

build_breathing_plan

Read-onlyIdempotent

Return a 7-day breathing plan for one goal (sleep, stress, anxiety, focus or energy): when to practise, a habit to attach it to, one practice per day that builds gradually, and how to review the week. Each day names the timer that runs it. Use it when the user wants a routine, a habit or a plan over several days rather than one session now. Nothing is saved or scheduled; the user comes back each day. 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": {
      "goal": "<goal>"
    },
    "name": "build_breathing_plan"
  }
}

Input Schema

Name	Required	Description	Default
`goal`	Yes	What the plan is for: sleep, stress, anxiety, focus or energy.

Output Schema

Name	Required	Description	Default
`days`	Yes
`goal`	Yes
`when`	Yes
`anchor`	Yes
`review`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: nothing is saved or scheduled and the user returns each day, plus the output is text only with no timer displayed — resolving a potential confusion with the earlier claim that each day 'names the timer that runs it'.

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?

It is front-loaded with the returned artifact and its contents, then the usage condition, then constraints. The one long first sentence packs several facts but each earns its place; minor redundancy in restating the goal list and the timer/wording clarification.

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?

For a one-enum-parameter, read-only generator with an output schema, the description covers everything an agent needs: what is produced, which goal to supply, that nothing is persisted or scheduled, and that the result is text only. Return-value detail is correctly left to the output schema.

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?

There is a single required parameter with 100% schema description coverage and a documented enum, so the schema already does the work. The description only repeats the five goal values without adding selection guidance, such as how to choose between 'stress' and 'anxiety'. Baseline 3 is appropriate.

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?

The description states a specific verb and resource ('Return a 7-day breathing plan') and enumerates the plan's contents: practice timing, habit anchor, one gradual practice per day, and a week review. It also separates itself from single-session tools by saying the user wants a plan 'over several days rather than one session now', so an agent can distinguish it without opening the schema.

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 gives a clear selection condition ('when the user wants a routine, a habit or a plan over several days rather than one session now'), which effectively excludes the case for a session tool. It stops short of naming concrete alternatives such as start_breathing_session or find_breathing_practice, so routing is inferred rather than explicit.

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?