Skip to main content
Glama

get_status

Retrieve current playback status—state, file path, position, duration, volume, speed, and resume key—to check what is playing and where playback stands.

Instructions

Get current playback status including state, file, position, duration, volume, and speed. file is the path the user gave; key is what resume points and bookmarks are filed under (the same string, except for a mounted disc, where it identifies the disc rather than the drive) and label is a disc's volume name.

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_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it is nominally a read-only getter, but that is only implied by 'Get'. It does valuable work defining output semantics — 'file' is the user-supplied path, 'key' is the bookmark/resume anchor and diverges for mounted discs, 'label' is the disc volume name — but says nothing about behavior when nothing is loaded or whether an error is raised.

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?

The capability statement is front-loaded in the first sentence, with the terminology clarification following. The second sentence is dense but earns its length because no output schema exists to document file/key/label elsewhere.

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?

Since there is no output schema, the description must characterize the return shape, and it does so field by field, including the tricky key-vs-file distinction. Only the idle/no-media behavior and any failure modes are left unaddressed for an otherwise complete zero-parameter snapshot tool.

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 the baseline is 4, and the description correctly does not invent any. Its terminology explanation applies to returned fields rather than inputs, which is a reasonable use of the space rather than a substitution for parameter documentation.

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 a specific verb and resource ('Get current playback status') and enumerates exactly what is included: state, file, position, duration, volume, speed. This is clearly distinguishable from narrower getters like get_position, though the description never explicitly names that alternative.

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?

No when-to-use or when-not-to-use guidance appears anywhere. The enumerated field list implies this is the comprehensive snapshot, but an agent facing overlapping siblings such as get_position or describe_frame gets no explicit routing rule or stated prerequisites from the description.

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