Skip to main content
Glama

get_live_stream

Read-onlyIdempotent

Return one live stream. Does not include stream_key.

`ingest` has the RTMP and RTMPS server URLs (no key) and, after start,
the encoder `host`. SRT and WebRTC ingest URLs are never included.
A missing or foreign stream is `code: stream_not_found`.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "stream_id": "<stream_id>"
    },
    "name": "get_live_stream"
  }
}

Input Schema

NameRequiredDescriptionDefault
stream_idYesLive stream id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / stream_id / pattern
      Added value: +"^[A-Za-z0-9_-]{1,64}$"
  2. Added
  3. Removed
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description doesn't need to restate safety. It adds real value beyond them: the contents of the `ingest` block (RTMP/RTMPS URLs, encoder `host` after start), the explicit guarantee that SRT/WebRTC ingest URLs are never returned, and the exact error code (`stream_not_found`) for missing or foreign streams.

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 identification sentence is front-loaded and every subsequent line carries distinct information (excluded field, ingest contents, error code). The middle sentence ('`ingest` has ... and, after start, the encoder `host`') is slightly compressed and awkward to parse, but nothing is wasted.

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 an output schema present, the description needn't enumerate return fields, yet it still highlights the fields an agent is most likely to mis-assume (stream_key absence, ingest URL types) plus the error contract. The only gap is that it never points at get_live_stream_health for status questions.

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?

Schema coverage is 100% and the single `stream_id` parameter is fully documented in the schema with pattern and length constraints, so the description is not required to compensate. It adds the failure semantics for a foreign id but no additional meaning about the parameter itself, which is the baseline case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Return one live stream') and immediately scopes it by excluding `stream_key`, which distinguishes it from the sibling get_live_stream_key without naming it. An agent can tell single-item retrieval apart from list_live_streams on the first line.

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 'Does not include `stream_key`' note implies the alternative for key retrieval, and the health sibling is left unaddressed. There is no explicit when-to-use / when-not statement, so the routing guidance is implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.