2hives: Sleep & Meditation

Find a focus session

find_focus

Read-only

Use this when the user wants to concentrate or get into work: a focus session before studying, a study break, deep work, before an exam, a short reset between tasks, or help to stop procrastinating and start. Not for medical questions, emergencies or a crisis. Not for general chat about meditation. Not for sleep audio (use find_sleep_sessions) or for breathing exercises (use find_breathing).

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

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

A3.7/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 fully covered by structured data. The description adds only routing context and nothing about what is returned or how results behave; with annotations carrying the behavioral load, a 3 is appropriate.

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?

Use triggers are front-loaded before the exclusion clauses, and every clause carries routing information rather than filler. The 'Not for ... Not for ... Not for ...' fragments are slightly listy but each earns its place by blocking a realistic misroute.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The definition is strong on routing but thin overall: it never says what a 'focus session' actually is (audio? guided? list of results?) and omits the fallback behavior when a language is unavailable, which the schema mentions. Output schema and annotations cover returns and safety, but the core object being retrieved remains undefined, leaving a gap for a discovery tool.

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%, with voice, language and length_min all documented inline including enum meaning, defaults and the beta-language caveat. The description adds nothing about parameters, so the baseline 3 applies.

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 conveys the resource indirectly through a dense list of user intents ('before studying, a study break, deep work, before an exam, a short reset'), which makes the focus-session nature unmistakable and clearly distinct from sleep or breathing siblings. It never states an explicit verb+resource ('returns focus session audio'), relying instead on intent triggers, so it falls short of a textbook 5.

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 gives explicit when-to-use triggers, explicit when-not-to-use cases ('medical questions, emergencies or a crisis', 'general chat about meditation'), and names two concrete alternatives with their routing conditions (find_sleep_sessions, find_breathing). An agent has everything needed to route correctly.

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?