Skip to main content
Glama

Mellow Mountain Radio

by com.mellowmountainradio.mcp
OverviewDiscussionsAdmin

Sound Session

get_sound_session
Read-onlyIdempotent

Recommends a KAZM sound healing session — binaural or tonal — based on the listener's goal or current time of day. Returns session name, description, frequency, duration, and link.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoListener's intent — omit to get a time-of-day recommendation

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reasonNo
recommendedYes
also_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedOutput schema / additionalProperties
      Previous value: -falseNew value: +true
    • removedOutput schema / properties / also_available / items / type
      Removed value: -"string"
    • addedOutput schema / properties / recommended / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": {},
+    "type": "object"
+  }
+]
    • removedOutput schema / properties / recommended / type
      Removed value: -"string"
    • changedOutput schema / required
      Previous value: -[
-  "recommended",
-  "reason",
-  "also_available"
-]New value: +[
+  "recommended"
+]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "also_available": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "reason": {
+      "type": "string"
+    },
+    "recommended": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "recommended",
+    "reason",
+    "also_available"
+  ],
+  "type": "object"
+}
  3. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare safe, read-only, idempotent behavior. Description adds details on return fields (session name, description, frequency, duration, link) and decision logic (goal or time-of-day). No contradictions.

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?

Two efficient sentences, no redundancy, main action front-loaded. Every sentence adds value.

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

Completeness5/5

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

Given simple input, rich annotations, and presence of output schema, description covers all needed behavioral and input context. No gaps.

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

Parameters5/5

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

Single parameter 'goal' with enum and 100% schema coverage. Description adds critical context: omitting goal yields a time-of-day recommendation, which is not in schema.

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?

Description clearly states the tool recommends a KAZM sound healing session based on goal or time, with specific verb 'Recommends' and resource 'sound healing session'. Distinguishes from siblings by being a recommendation tool rather than information retrieval.

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?

Implies usage when a listener wants a session recommendation. Lacks explicit when-not-to-use or alternatives, but no sibling tool provides similar functionality, so context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mellow Mountain Radio 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