2hives: Sleep & Meditation

Talk live

start_live_session

Use this when an adult asks to talk to the guide live, one to one, by voice, instead of playing a recorded session. Not for medical questions, emergencies or a crisis. Not for general chat about meditation. Not for choosing a recorded session (use find_sessions).

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

Input Schema

Name	Required	Description
`tap`	No	The 18+ tap token returned by keep_progress for this conversation; leave empty if there is none.
`mood`	No	What the conversation is for.
`topic`	No	Optional, in the user''s own words, up to 200 characters.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the description only needed to add what the annotations cannot. It contributes real value with the eligibility and crisis-escalation boundaries, but says nothing about what actually happens on invocation: whether a guide is connected immediately, expected wait, duration, or what an empty tap token implies for the 18+ gate.

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?

Four short sentences, front-loaded with the primary trigger followed by hard exclusions, with zero filler or restatement of the title. Every clause carries routing information.

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

Completeness3/5

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

All parameters are optional, there is no output schema, and the annotations are clear, so a lot is already covered. Still, for a live-connection tool the description omits the outcome behavior (connection latency, guide availability, failure mode), which is the main thing an agent cannot infer from structured fields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, and the description's 'an adult asks' and 'one to one... by voice' framing corroborates the 18+ tap token requirement without restating the schema. It does not add syntax or format detail for mood or topic, so it stays near the baseline rather than above it.

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 concrete verb and resource ('talk to the guide live, one to one, by voice') plus the key differentiator from recorded playback. The one-to-one framing also separates it from the group option without needing to name it.

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 trigger ('when an adult asks to talk to the guide live') and three explicit exclusions (medical/emergency/crisis, general meditation chat, choosing a recorded session), naming find_sessions as the alternative for that last case. An agent can route correctly from this text alone.

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?