2hives: Sleep & Meditation

Browse the library

browse_library

Read-only

Use this when the user wants to look through everything 2hives has for a topic or language, rather than get one session. 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": "browse_library"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	No	Limit to one kind: sleep, calm, breath (breathing), focus, body (body scan), nature (nature sounds with a voice). Default all.	all
`page`	No	Page number, starting at 1.
`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.

Output Schema

Name	Required	Description	Default
`ui`	No
`host`	No
`page`	No
`view`	No
`ended`	No
`total`	No
`status`	No
`profile`	No
`ai_voice`	No
`language`	No
`sessions`	No
`help_lines`	No
`longer_url`	No
`language_changed_from`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive, closed-world), and the description adds genuine context on top: this returns a broad topic/language-scoped listing rather than a single result, and it should not be used for medical/emergency/crisis situations. Return shape and paging semantics are left to the output schema and parameter descriptions, which is appropriate.

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 usage trigger, followed by the negative routing rules. There is no filler or restatement of the title.

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 only three optional, fully documented parameters, existing annotations, and an output schema, the description supplies what structured data cannot: when to browse versus fetch one item, and which user intents to route elsewhere. Only the absence of a named alternative for the excluded cases keeps it from being fully complete.

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%, and the schema itself already carries rich parameter guidance, including the instruction to always pass the user's language and the beta caveats for hi/ko/hu. The description adds nothing about 'kind', 'page', or 'language', so the baseline of 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 states a specific action and scope: 'look through everything 2hives has for a topic or language,' and explicitly contrasts it with 'get one session,' which lets an agent separate browsing the catalog from fetching a single item. The resource is named loosely ('everything 2hives has') rather than as sessions/audio, so it is clear but not maximally precise.

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 an explicit trigger ('use this when the user wants to look through everything...') and explicit exclusions (medical questions, emergencies, crisis, general chat about meditation). It stops short of naming the alternative tools to use in those excluded cases, so the agent must infer the redirect target.

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?