Skip to main content
Glama

stop_live_stream

Destructive

Stop a live stream. Call this only when the user asks to stop it.

Already stopped comes back as `code: live_api_error` (live API 406). Do
not retry that.

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": "stop_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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations cannot express: the exact failure shape when the stream is already stopped (live_api_error, HTTP 406) plus an explicit 'do not retry' instruction, which is directly actionable and consistent with idempotentHint=false.

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?

Two short sentences, both front-loaded with the highest-value information: the action first, then the invocation gate, then the error contract. No filler, no restatement of the title, and nothing that could be cut without losing information.

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 values need no explanation, and annotations carry the destructive flag. The description covers the action, the invocation condition, and the main error path. It stops short of stating the resulting stream state or whether the stream can be restarted afterward, which is a modest gap for a state-transition tool.

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 description coverage is 100% and the single stream_id parameter is documented with a regex pattern and length bounds in the schema. The description adds no meaning beyond that, so the baseline of 3 applies.

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 opens with a specific verb+resource: 'Stop a live stream.' That cleanly separates it from start_live_stream and delete_live_stream, though it never explicitly names those siblings or clarifies stop-vs-delete semantics, which is the one distinction an agent most needs here.

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?

It gives an explicit gating condition ('Call this only when the user asks to stop it'), which is real when-to-use guidance and prevents unsolicited invocation. However, it offers no when-not guidance relative to alternatives like delete_live_stream or update_live_stream, so the agent must infer the boundary from names alone.

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.