2hives: Sleep & Meditation

Make a personal session from words

create_personal_session_text

Use this when an adult describes in their own words what a session should be about and wants one made just for them, in a host that allows free text. Not for medical questions, emergencies or a crisis. Not for general chat about meditation. Not for choosing an existing session (use find_sessions).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wish": "<wish>"
    },
    "name": "create_personal_session_text"
  }
}

Input Schema

Name	Required	Description
`tap`	No	The 18+ tap token returned by keep_progress for this conversation; leave empty if there is none.
`wish`	Yes	The listener''s wish in their own words, up to 200 characters, no personal details needed.
`length_min`	No	Length in minutes, 5 or 10.

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 this is a non-destructive, closed-world write (readOnlyHint=false), so the burden is lighter. The description adds genuinely non-structured context: an 18+ eligibility requirement, a host capability prerequisite (free-text hosts only), and hard safety boundaries that determine when not to act at all. It does not say what comes back or whether the created session is immediately playable, which keeps it below a 5.

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-loaded with the primary trigger, then a compact chain of exclusions, one of which names the alternative. Every sentence carries routing value, though the three consecutive 'Not for' fragments read as a list rather than prose and could be tightened slightly.

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?

For a creation tool with no output schema and full schema coverage, the definition covers eligibility, environment preconditions, exclusions, and the sibling alternative. The only real omission is outcome behavior — whether a session is generated immediately, whether it may be rejected, or what identifier the agent receives.

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 'wish', 'tap' and 'length_min' are already documented with examples and an enum. The description's phrase 'in their own words' only loosely reinforces the 'wish' parameter and says nothing about the tap token or length choice, so 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 ('describes in their own words what a session should be about and wants one made just for them'), plus the environment precondition ('in a host that allows free text'). It explicitly distinguishes itself from find_sessions for choosing an existing session, so an agent can route without opening a 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 when-to-use trigger (adult free-text description of a desired session) and three explicit exclusions: medical/emergency/crisis, general chat about meditation, and choosing an existing session with the named alternative find_sessions. This is the strongest possible guidance pattern for sibling routing.

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?