Skip to main content
Glama

Get Live Status

get_live_status
Read-onlyIdempotent

Read back the current state of a live stream you created, so a restarted producer can reconcile instead of starting a duplicate. Only returns streams started by this credential, within the last 24 hours. Returns notification_id and correlation_id, then the stored display state (state, progress, message, category, template, accent_override, eta_at, deadline_at, duration_seconds, metrics, prompt, options, left, right, center, steps, current_step, started_at, value, value_label, delta, trend, stats, segments, current_segment), action_state, and updated_at; a claim request also returns its title and claim (status, by, at, late). Fields you never set come back as null rather than being omitted, so a matchup/metrics/countdown/question stream can be resumed without re-sending content.

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": {
      "invite_code": "<invite_code>",
      "correlation_id": "<correlation_id>"
    },
    "name": "get_live_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
invite_codeYesRoom invite code.
correlation_idYesThe stream key used when the stream was started.

Output Schema

NameRequiredDescriptionDefault
resultYesPurpose-built PingRoom result with credential and account fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already establish readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely new behavior: credential-scoped results, a 24-hour lookback window, and the rule that unset fields return as null rather than being omitted. The null-vs-omitted semantics are the most valuable disclosure because they tell a producer it can resume without re-sending content. It does not discuss error behavior when the stream is older than 24 hours or belongs to another credential.

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

Conciseness2/5

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

The opening two sentences are well front-loaded and earn their place, but the remainder is a single sprawling sentence enumerating roughly thirty return field names. Since an output schema exists, that enumeration is largely redundant and buries the one non-obvious point (nulls for unset fields). The description is significantly longer than its useful content warrants.

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?

The tool is simple (two required params, flat schema, output schema present), and the description covers scope, retention window, and null semantics, which is what an agent actually needs to call it correctly. The redundant field list neither adds nor subtracts much, and the return values themselves are documented by the output schema.

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% with only two required parameters, so the schema already explains both invite_code and correlation_id. The description adds no format, constraint, or matching detail beyond what the schema states; the phrase 'a live stream you created' only loosely gestures at correlation_id.

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 first clause gives a specific verb and resource ('Read back the current state of a live stream you created') plus the motivation (reconcile instead of starting a duplicate). It is clear on its own, but it never distinguishes itself from the similarly named sibling 'live_status', so an agent has no textual basis for choosing between the two.

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?

It states a concrete usage context — a restarted producer reconciling its own stream rather than creating a duplicate — and scopes the result set to streams started by this credential within the last 24 hours. It stops short of naming alternatives or stating when not to use it (e.g., versus live_status), which keeps it out of 5 territory.

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.

Resources