Skip to main content
Glama
virwave

virwave-breathe

Official
by virwave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start a breathing session

breathe

Generate an animated breathing session as a self-contained HTML page, save it to your computer, and open it in your browser. The session stays still until you press Begin, providing a calm visual guide for your breath.

Instructions

Creates an animated VirWave breathing session as a self-contained HTML page, saves it on this computer, and returns its file path. Unless out_dir is given, the page also opens in the person's default browser (they can turn that off in settings). The page opens at rest and starts when the person presses Begin, so nothing moves without their say-so. With no inputs, it plays the default Circle 4-8 Breathing session, which has no breath holds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
shapeNoShape to draw. Each pattern lists the shapes it can use; defaults to the pattern's first. box: A square whose outline draws itself once per breath cycle. triangle: A triangle whose outline draws itself once per breath cycle. circle: A ring that draws itself once per breath cycle, with no corners to turn. focus-point: A calm point drifting slowly across the field. infinity: A continuous figure-eight with no start or end. ripple: Rings spreading out from a point of contact. color-field: Slow colour folding into itself.
cyclesNoExact number of breath cycles. Takes precedence over minutes.
minutesNoApproximate session length; rounded to whole breath cycles.
out_dirNoDirectory to write the page into, for a client that shows the page itself (for example, by publishing it as an Artifact). When set, the page is not opened in the browser. When left out, the page is saved to the person's chosen folder (by default a VirWave Breathe folder in the system temp directory) and opened in their browser.
patternNoPattern id from list_patterns. Defaults to in-out-extended-exhale. list_patterns marks each hold-free pattern with "holdFree": true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Since all annotations are false, the description carries the full disclosure burden. It transparently mentions file creation, browser opening, the page starting only on user press of 'Begin', and the no-breath-hold default. These side-effect details go beyond the schema and give the agent a clear behavioral profile. It does not cover potential file overwriting, but destructiveHint=false mitigates that concern.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, each earning its place: the main action and result, browser behavior with out_dir exception, user-initiated start, and default session details. It is front-loaded with the core function, has no filler, and is easily scannable.

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 tool with no output schema, the description adequately explains the return value (file path) and key behaviors. It is largely complete, but it does not address how to choose between this tool and sibling start_session, and the label 'Circle 4-8 Breathing' does not directly match the schema's enum terms, which could cause minor agent confusion. Overall, still quite complete given the rich parameter 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?

Schema coverage is 100%, so each parameter already has a thorough description. The description adds default-context ('default Circle 4-8 Breathing session') and the out_dir behavior, but does not clarify the cycles/minutes precedence or other parameter relationships beyond what the schema already states. Baseline 3 is appropriate when the schema carries the semantic load.

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 ('Creates'), resource ('animated VirWave breathing session as a self-contained HTML page'), and outcome ('returns its file path'). The level of detail about file creation and browser opening clearly distinguishes it from the sibling tools list_patterns and start_session, even without naming them.

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

Usage Guidelines3/5

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

The description gives conditional guidance around out_dir ('Unless out_dir is given, the page also opens in the person's default browser'), which tells the agent when to set that parameter. However, it does not explicitly contrast this tool with sibling start_session or provide when-not-to-use guidance, so usage context is implied rather than explicit.

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

Deploy Server

Other Tools