Skip to main content
Glama
Sign In

2hives: Sleep & Meditation

by com.2hives
OverviewDiscussionsAdmin

Start 7 calm nights

start_sleep_plan

Use this when the user wants a gentle seven-night wind-down routine and gives, or can give, a usual bedtime and how many minutes they would like each evening (5, 10, 20 or 30). Not for medical questions, emergencies or a crisis. Not for general chat about meditation.

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": {
      "bedtime": "<bedtime>",
      "length_min": "<length_min>"
    },
    "name": "start_sleep_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
tapNoThe 18+ tap token returned by keep_progress for this conversation; leave empty if there is none.
todayNoThe listener's local date, YYYY-MM-DD.
bedtimeYesThe usual bedtime, 24-hour HH:MM, for example 22:00.
languageNoAudio language as a BCP-47 code.
length_minYesMinutes for each evening, 5, 10, 20 or 30.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a non-destructive, closed-world write, so the agent knows the safety profile. The description adds the prerequisite inputs and the seven-night scope, but does not say what is actually created (sessions, audio, schedule) or what happens on repeat invocation. For a creation tool, that is adequate but thin.

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?

Three short sentences, front-loaded with the trigger condition followed by exclusions; nothing is wasted. The parenthetical listing the allowed minute values duplicates the schema enum, a minor redundancy.

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 complete schema coverage, no output schema, and annotations covering safety, the description supplies the needed trigger, prerequisites, and scope. The main remaining gap is not explaining what the created plan contains or how the 18+ tap token interacts with it, though the schema describes that token.

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%, so all five parameters including the tap token, local date, and language are already documented. The description only restates bedtime and the minute options already enumerated in the schema, adding no new semantics. 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 names the concrete artifact ('a gentle seven-night wind-down routine') and the inputs that define it, so an agent can tell this initiates a sleep plan rather than a live session or library lookup. It never uses an explicit verb like 'create' or 'start', leaning on the name for that, which keeps it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states exactly when to use it (user wants a seven-night wind-down routine and supplies or can supply bedtime plus minutes) and explicitly excludes medical questions, emergencies, crisis, and general meditation chat. It does not name a specific sibling tool to route those excluded cases to, so it stops short of full alternative 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 toolsInspect
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