2hives: Sleep & Meditation

Find a sleep session

find_sleep_sessions

Read-only

Use this when the user wants sleep audio: a bedtime wind-down, a quiet evening session, or a short nap. Plays a guided sleep session. Not for medical questions, emergencies or a crisis. Not for general chat about meditation. Not for a daytime break, focus or breathing exercises: use find_focus or find_breathing for those.

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_sleep_sessions"
  }
}

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.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description only adds the domain/safety boundary. However, "Plays a guided sleep session" sits oddly against a read-only find tool and against the separate play_session sibling, leaving playback semantics ambiguous. No mention of rate limits, language fallback behavior, or what happens when a requested language is unavailable.

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?

Usage condition is front-loaded in a single opening sentence, and the negative routing follows immediately. The three-sentence negative block is somewhat repetitive in structure, but each clause routes to a different sibling or safety case, so little is wasted.

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?

An output schema exists, so return values need not be explained, and all three optional parameters are covered by the schema. What remains thin is the playback/return behavior implied by "Plays a guided sleep session," which is the one thing an agent cannot resolve from structured fields.

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 fully documented in the schema and the baseline is 3. The description contributes only indirectly, via "short nap" implying a length choice, and adds no constraint, default, or language-fallback guidance of its own.

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?

"Find sleep sessions" is stated through concrete user intents (bedtime wind-down, quiet evening session, short nap) plus a specific verb/resource pairing, so an agent knows exactly what the tool returns. The exclusions ("not a daytime break, focus or breathing exercises") separate it from nearby siblings without needing their schemas.

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?

Explicit when-to-use cases are listed first, followed by explicit when-not cases, followed by named alternatives (find_focus, find_breathing). Safety boundaries (medical questions, emergencies, crisis, general meditation chat) are also called out, which is exactly the routing information an agent needs.

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?