Skip to main content
Glama

recording_status

Read-onlyIdempotent

Check whether a call recording is active, how long it has run, and recent sound levels for each side; use -120 dB to spot a side capturing no audio.

Instructions

Whether a recording is in progress, for how long, and the recent sound levels of each side (-120 dB on the other side means no sound is being captured).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive behavior, so safety is covered. The description adds genuinely non-obvious diagnostic context — that -120 dB on one side means nothing is being captured — which is the kind of signal an agent could not get from annotations or the schema.

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 sentence with the core fact front-loaded ('Whether a recording is in progress') and the loudness detail tucked into a parenthetical. Everything earns its place; the only blemish is the awkward mid-phrase line break.

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?

An output schema exists, so return shape need not be restated, and the description instead supplies the interpretation of the most easily misread field. For a zero-parameter read tool with full annotations, nothing an agent needs to call and use it correctly is missing.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing to disambiguate and the baseline is 4. The description correctly spends no space on arguments.

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?

States exactly what is returned: recording-in-progress flag, duration, and per-side sound levels. That is specific enough to separate it from the start/stop/transcript siblings, but it never names a sibling or explicitly frames itself as the status counterpart to start_recording/stop_recording.

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?

Usage is only implied — an agent can infer this is the read-only probe to poll while recording, versus start_recording and stop_recording which mutate state. There is no explicit 'use this before calling stop_recording' or any exclusion, so the routing is left to inference.

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