2hives: Sleep & Meditation

Save a session

save_session

Use this when the user wants to keep a session to come back to: save this, add it to my list, favourite it. 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": {
      "session_id": "<session_id>"
    },
    "name": "save_session"
  }
}

Input Schema

Name	Required	Description
`tap`	No	The token from keep_progress for this conversation; leave empty if there is none.
`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.
`session_id`	Yes	The session id from find_sessions or play_session.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The annotations already indicate a non-read-only, non-destructive, non-open-world operation, so the agent knows this is a safe write action. The description adds the intended effect of keeping a session for later, but it does not explain whether repeated saves are idempotent, where the session is saved, or what confirmation follows.

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?

The description is short and front-loads the primary user intent before listing exclusions. The exclusion sentences are useful routing guardrails, though they repeat the "Not for" pattern and take space relative to the core save action.

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 simple, low-complexity save operation with full schema coverage and annotations covering safety, the description provides enough context to select and invoke the tool. Minor gaps remain around the persistence behavior and confirmation details, but these are not necessary for correct invocation.

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 the schema already documents session_id, tap, and language thoroughly. The description adds no parameter-specific detail beyond that, which is acceptable but does not add meaning beyond the structured input definition.

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 clearly states the action and resource: saving a session so the user can return to it, with concrete user phrasings like "save this" and "add it to my list." It does not explicitly differentiate from sibling tools such as like_session or unsave_session, and the word "favourite" could blur that boundary slightly.

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 gives clear when-to-use guidance (the user wants to keep a session to come back to) and explicit when-not-to-use cases (medical questions, emergencies, crisis, general meditation chat). It does not name alternative tools, such as like_session or unsave_session, so the alternative-routing element is missing.

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?