Skip to main content
Glama
virwave

virwave-breathe

Official
by virwave
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Start a breathing session

breathe

Create an animated breathing session you follow with your eyes to calm down or reset. It appears in your chat or as a file.

Instructions

Creates an animated VirWave breathing session the person can follow with their eyes. Invoke it when someone asks for a breathing break, a breathing exercise, guided breathing, or a moment to calm down, relax, or reset: the visual session is the breathing break. In a client that supports MCP Apps (Claude Desktop, for example), the session appears in the chat itself, and no browser opens and no file is saved unless out_dir is given or the person has turned on saving a copy. In any other client, it is saved as a self-contained HTML page on this computer and, unless out_dir is given, opens in the person's default browser (they can turn that off in settings). The result says which happened. Either way the session 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. Changed1 schema field changedv1.2.0
    • changedInput schema / properties / pattern / enum
      Previous value: -[
-  "in-out-equal-4",
-  "in-out-extended-exhale",
-  "in-out-quick-2",
-  "in-hold-out-equal-4",
-  "in-hold-out-extended-exhale",
-  "in-hold-out-quick-2",
-  "box-equal-4",
-  "box-quick-3",
-  "4-7-8-signature"
-]New value: +[
+  "in-out-equal-4",
+  "in-out-slow-5",
+  "in-out-extended-exhale",
+  "in-out-quick-2",
+  "in-hold-out-equal-4",
+  "in-hold-out-extended-exhale",
+  "in-hold-out-quick-2",
+  "box-equal-4",
+  "box-quick-3",
+  "4-7-8-signature"
+]
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations are all false, so they carry no behavior signal and the description must do the work—it does. It details the two client-type behaviors (appears in chat vs. saved HTML that opens in a browser), when files are saved, how out_dir suppresses the browser, that nothing starts until the user presses Begin, and the no-input default.

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?

The description is a dense single paragraph of about 200 words, but every clause earns its place: trigger conditions, client-specific behavior, default behavior, and user consent to start. It front-loads the most decision-relevant facts and uses parentheticals to keep asides from derailing the main thread.

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?

Given there is no output schema, the description notes 'The result says which happened'—minimal but sufficient expectation-setting for return behavior. It also covers defaults, side effects, and the two client environments, leaving little an agent needs to call it safely.

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?

With 100% schema coverage the baseline is 3; the description exceeds it by explaining the no-input default ('default Circle 4-8 Breathing session'), the effect of out_dir on browser and file behavior, and noting the default has no breath holds. It avoids re-documenting individual parameters, which the schema already covers thoroughly.

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 opens with a specific verb and resource: 'Creates an animated VirWave breathing session the person can follow with their eyes.' It clearly identifies the tool's function, but it never contrasts with sibling start_session, so a caller must infer the boundary from the word 'breathing' rather than explicit differentiation.

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?

The description gives explicit when-to-use conditions: 'Invoke it when someone asks for a breathing break, a breathing exercise, guided breathing, or a moment to calm down, relax, or reset.' It clarifies the session itself is the break, but offers no when-not-to-use guidance or reference to alternatives like start_session or list_patterns.

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