2hives: Sleep & Meditation

Make a personal session

create_personal_session

Use this when the user wants a session made for them from a short menu, choosing the kind, the length, the voice and a theme, for example a quiet 5 minute session with a female voice. Not for medical questions, emergencies or a crisis. Not for free-text wishes (use create_personal_session_text, which needs a signed-in adult account): pick from the menus.

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": "create_personal_session"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	What the session is for. Pick from the user's words: sleep (sleep audio, a nap), calm (wind down, before a meeting), breath (breathing), focus (study, work), body (body scan), nature (nature sounds with a voice). Default: calm.	calm
`theme`	No	Theme from a fixed list: quiet (few words), breath, body, nature (nature sounds), pause (a short pause). Default quiet.	quiet
`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 20 (longer sessions are on 2hives.com). 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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: safety guardrails (medical/emergency/crisis), a constraint that input must come from fixed menus, and an account prerequisite noted for the sibling. It stops short of saying whether creation consumes quota or what happens to the session afterward (play/schedule), which would be the last piece.

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?

Front-loads the positive use case, then the exclusions, then the alternative — a sensible order with no filler sentences. The parenthetical about the sibling needing 'a signed-in adult account' is slightly more detail than the routing decision requires, but it is not 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?

With an output schema present, return values need no explanation, and all five optional params are fully documented in the schema. The definition covers when/when-not/alternative adequately for a creation tool. What is left implicit is the next step after creation — whether the agent should then call play_session or get_session_status — which matters given those siblings exist.

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% with enums and per-field descriptions, so the schema already carries parameter meaning. The description adds only a worked mapping example ('a quiet 5 minute session with a female voice') that shows how user phrasing lands on theme/length/voice — helpful but marginal. Baseline 3 applies.

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?

States a specific verb and resource ('a session made for them') plus the exact selection surface ('from a short menu, choosing the kind, the length, the voice and a theme'). It immediately distinguishes itself from the free-text sibling by name, so an agent can route without opening the schema.

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?

Gives an explicit positive trigger ('when the user wants a session made for them'), explicit exclusions ('not for medical questions, emergencies or a crisis'), and names the alternative for the out-of-scope case ('use create_personal_session_text'). The 'pick from the menus' instruction closes the loop on what not to do here.

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?