Skip to main content
Glama

Get playing song by room

songrequests_playing_global
Read-only

Get the currently playing song in a media request room by specifying provider and room, not channel.

Instructions

Get the song currently playing in a media request room, looked up by provider and room instead of channel. StreamElements does not document these parameters.

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

Input Schema

NameRequiredDescriptionDefault
roomNoRoom (undocumented)
providerNoProvider (undocumented)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds only the caveat that StreamElements does not document these parameters, which sets expectations but does not describe return behavior, failure modes, or auth requirements. With annotations carrying the safety burden, this is an adequate but modest addition.

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?

Two short sentences with the purpose front-loaded and the undocumented-parameters caveat second. There is no filler, though the second sentence is borderline meta-commentary rather than actionable behavioral detail.

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?

For a low-complexity read tool with two optional parameters, the description establishes what it does and warns that the parameters are undocumented. However, with no output schema it should describe the returned song shape or empty-state behavior, which it omits entirely.

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

Parameters3/5

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

The schema nominally covers both parameters, but their descriptions are only '(undocumented)', and the description merely echoes that same fact with 'StreamElements does not document these parameters'. It adds no format hints, valid values, or examples, so it sits at the baseline for high nominal schema coverage.

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 uses a specific verb ('Get') plus resource ('song currently playing') and scope ('in a media request room'), and it explicitly distinguishes the lookup axis as 'provider and room instead of channel'. That differentiates it from the channel-based sibling, though it does not name that sibling explicitly.

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?

The phrase 'looked up by provider and room instead of channel' tells the agent the condition under which this variant is appropriate versus a channel-based lookup. It gives clear context but does not explicitly name the alternative tool or state when not to use this one.

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