2hives: Sleep & Meditation

Change my settings

set_preferences

Use this when the user wants to change how their sessions sound or are chosen: a voice, a language, a length, the music layer on or off, or Quiet mode. Not for medical questions, emergencies or a crisis. Not for general chat about meditation.

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

Input Schema

Name	Required	Description
`tap`	No	The token from keep_progress for this conversation; leave empty if there is none.
`music`	No	The music layer on or off.
`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.
`voice_id`	No	A voice id as returned by find_sessions.
`length_min`	No	Preferred session length in minutes.
`quiet_mode`	No	Quiet mode hides badges and progress.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare this is a non-destructive, non-open-world mutation, so the safety profile is covered. The description adds the behavioral scope of what can change, which is useful. However, with all parameters optional, the key behavioral question — whether omitted fields are left unchanged (partial update) — is never answered, nor is persistence of changes across sessions.

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?

Three short sentences, front-loaded with the primary trigger, followed by tight exclusions. No redundant phrasing and nothing buried mid-sentence; every clause carries routing information.

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 6-parameter, all-optional mutation with full schema coverage and clear annotations, the description supplies enough to select and invoke it correctly, and no output schema is needed since only the language-fallback response matters and that is documented in the schema. The remaining gap is the partial-update/omitted-field behavior an agent would want before calling it.

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 every parameter including the tap token, BCP-47 language codes, length bounds and voice_id source is already documented in the schema. The description only restates the field list in plain language without adding format, constraint, or interaction semantics. Baseline 3 is appropriate.

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 gives a specific verb ('change') and enumerates the exact settings affected: voice, language, length, music layer, and Quiet mode. It is clearly a preferences/settings mutation and cannot be confused with data-retrieval siblings. It stops short of a 5 because no sibling tool is named as the route for the excluded cases.

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?

The opening clause gives an explicit trigger ('when the user wants to change how their sessions sound or are chosen'), and two 'Not for' sentences carve out medical questions, emergencies, crises, and general meditation chat. That is clear when-to-use and when-not-to-use guidance. No specific alternative tool is offered for the out-of-scope cases, which keeps it from a 5.

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?