2hives: Sleep & Meditation

Find a breathing session

find_breathing

Read-only

Use this when the user wants a guided breathing exercise: a breathing break, box breathing, slow breathing, or a few minutes of breath before a meeting. Plays a short calm session. Not for medical questions, emergencies or a crisis. Not for general chat about meditation. Not for sleep audio (use find_sleep_sessions) or for focus (use find_focus).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_breathing"
  }
}

Input Schema

Name	Required	Description	Default
`voice`	No	Voice preference. Default any.	any
`language`	No	Audio language as a BCP-47 code (en, es, pt-BR, fr, it, ja, hi, ko, hu, or any other such as pl). Always pass the language the user writes in. If the language is not available the answer says so and gives the closest live one. hi, ko and hu are beta.
`length_min`	No	Length in minutes, 3 to 60. Default 10 when the user gives none.

Output Schema

Name	Required	Description	Default
`ui`	No
`job`	No
`tap`	No
`url`	No
`host`	No
`lang`	No
`view`	No
`ended`	No
`beacon`	No
`reason`	No
`status`	No
`profile`	No
`ai_voice`	No
`language`	No
`manifest`	No
`sessions`	No
`help_lines`	No
`queue_line`	No
`session_id`	No
`ai_voice_label`	No
`language_changed_from`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, closed-world operation, so the bar for behavioral disclosure is lower. The description adds that it plays a short calm session and adds important safety/scope exclusions, though it does not describe audio playback behavior or failure modes beyond what the schema covers.

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 compact and front-loaded: it leads with when to use the tool, gives concrete examples, then states exclusions and alternatives. Every sentence serves either use-case guidance or scope routing.

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?

Given that the schema is fully described, annotations cover safety, and an output schema exists, the description provides enough context for correct selection and invocation. It clearly separates breathing from sleep, focus, general meditation chat, and crisis handling.

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%, so voice, language, and length_min are already documented in the schema. The top-level description adds no parameter-specific meaning beyond what the schema provides, which makes the baseline 3 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: it plays a guided breathing session. It also names concrete use cases (breathing break, box breathing, slow breathing, pre-meeting breath) and distinguishes the tool from siblings such as find_sleep_sessions and find_focus.

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

Usage Guidelines5/5

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

It explicitly says when to use the tool, gives representative user intents, and lists clear exclusions including medical questions, emergencies, crisis, general meditation chat, sleep audio, and focus. It also routes sleep and focus requests to named alternatives.

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

All 2hives: Sleep & Meditation 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?