Skip to main content
Glama

get_recording_status

Check whether the current or last arrangement recording run finished, and report its stop position, transport state, and armed tracks.

Instructions

State of the current or last record_arrangement run (finished, reason, stop position), plus Arrangement Record, transport and armed tracks.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses the meaningful behavioral trait that the call falls back to the last completed run when nothing is currently running, and enumerates what state is reported, but it says nothing about side effects, cost, or what is returned when no run has ever occurred.

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 that front-loads the core purpose and then lists the returned state. It is efficient, though the parenthetical field list and the capitalized 'Arrangement Record' term add slight density without clarification.

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 zero parameters and an output schema present, the description needn't document return values in depth, and it still summarizes the key state fields. The only gap is the edge case of querying before any record_arrangement run has existed.

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 zero parameters, so there is no parameter semantics to add; the baseline for a parameterless tool applies. Nothing in the description contradicts the empty argument object.

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 names a specific resource and verb-equivalent: the state of the current or last record_arrangement run, and enumerates the fields returned (finished, reason, stop position, Arrangement Record, transport, armed tracks). An agent can distinguish this from record_arrangement (which starts a run) and stop_arrangement_recording without opening the schema, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not guidance and no reference to alternatives such as record_arrangement or stop_arrangement_recording. The phrase 'current or last' hints that this is a polling/status-check tool, but that is inference rather than stated guidance.

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