Skip to main content
Glama
Podcast MCP
by calebn

record_room_tone_tool

Instructs every recorded device to capture one minute of room tone immediately for consistent noise profiles, working only when lobby or stopped.

Instructions

Host Room tone: tell every recorded device to capture one minute of room tone now (lobby or stopped only).

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

Input Schema

NameRequiredDescriptionDefault
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full burden; it does disclose the broadcast nature ('tell every recorded device') and the fixed one-minute duration, which is useful. It omits what happens to devices that are not eligible, whether the capture is reversible, and permission requirements, which matters for a state-changing broadcast action.

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?

A single compact sentence with the core action and the precondition front-loaded, with no filler. The 'Host Room tone:' label prefix is slightly redundant with the tool name but does frame the operation.

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

Completeness3/5

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

With an output schema present, return values needn't be explained, and the description covers scope, duration, and eligibility state. For an un-annotated mutating broadcast tool it still lacks failure/skip behavior and any mention of the otherwise undocumented parameter.

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

Parameters2/5

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

Schema description coverage is 0% for the single optional 'project_path' parameter, and the description says nothing about it — no explanation of what the path scopes or what a null default means. The only parameter is therefore entirely undocumented outside of its name and type.

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 verb and resource ('capture one minute of room tone'), plus scope ('every recorded device') and a state precondition. It is distinguishable from siblings like fill_with_room_tone_tool or extract_room_tone_bed_tool, though it does not name an alternative explicitly.

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

Usage Guidelines3/5

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

The parenthetical '(lobby or stopped only)' gives a clear prerequisite state for calling the tool, which is real usage guidance. However, it never names an alternative tool or states what to do when the session is not in that state, leaving the agent to infer the fallback.

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

Deploy Server

Other Tools