Skip to main content
Glama

get_live_stream_health

Read-onlyIdempotent

Ingest health for a live stream, passed through from the live API.

Without a time window the live API uses the current or last session.
With `time_bucket` the samples are aggregated. The body has no secrets.
Report `video_bitrate` and `audio_bitrate` as kilobits per second.
A missing dropped-frames field does not mean no frames were dropped.
Do not invent that count.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax samples, 1–1000.
time_toNoWindow end.
stream_idYesLive stream id.
time_fromNoWindow start.
time_bucketNoAggregation bucket, e.g. 1m.

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 cover safety (readOnly, idempotent, non-destructive, closed-world), so the description's added value is in behavior: session fallback when no window is supplied, aggregation when time_bucket is set, absence of secrets in the body, and the critical caveat that a missing dropped-frames field means unknown rather than zero. What is not covered is pagination/limit behavior and error modes, keeping it below a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Five short lines, each carrying a distinct operational fact: source, default window, aggregation, payload safety, and unit/missing-field semantics. The 'Do not invent that count' warning is the only line that reads as model-directed, but it is short and reinforces a real data hazard.

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?

An output schema exists, so return structure need not be explained, yet the description usefully supplements it with units and the missing-field interpretation. For a read-only pass-through tool of this complexity the definition is largely sufficient; only pagination/limit semantics and failure behavior are absent.

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?

Schema coverage is 100%, so baseline is 3, but the description genuinely adds meaning the schema does not: time_bucket changes the result from raw samples to aggregates, and omitting time_from/time_to falls back to the current or last session. Units for bitrate fields are specified, though limit is left to the schema.

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 (ingest health of a live stream) and clarifies that values are passed through from the live API, which separates it from siblings like get_live_stream (metadata) or get_job_status. It never explicitly names an alternative, so the differentiation is inferable rather than stated.

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 context is implied by the default-window behavior ('Without a time window the live API uses the current or last session') and by the time_bucket aggregation note. There is no explicit statement of when an agent should call this instead of get_live_stream or get_job_status_detailed, nor any exclusions or prerequisites.

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.