Skip to main content
Glama

remove_simulcast_target

Destructive

Remove a simulcast target. Call this only when the user asks.

`target_id` comes from `add_simulcast_target` or the stream's
`simulcast_targets`. Do not invent it.

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>",
      "target_id": "<target_id>"
    },
    "name": "remove_simulcast_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
stream_idYesLive stream id.
target_idYesSimulcast target id.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already flag destructive=true, readOnly=false, idempotent=false, and openWorld=false, so the safety profile is covered. The description adds the useful precondition of user request and warns against inventing target_id, but it does not explain the effect of removal on an active simulcast or whether it is reversible.

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?

Three short sentences are front-loaded with the action and followed by the usage and parameter constraints. There is no redundant restatement.

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 low-complexity with two required parameters, full schema coverage, annotations, and an output schema. The description covers purpose, the user-intent guardrail, and target_id provenance; only a brief note on the effect of removal is 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 both parameters are already documented in the schema. The description adds real meaning for target_id by identifying where it comes from ('add_simulcast_target' or the stream's 'simulcast_targets') and warning not to invent it.

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?

The description opens with a specific verb and resource: 'Remove a simulcast target,' making the action immediately identifiable. It is distinguishable from the add_simulcast_target sibling by the verb and by the explicit source reference for target_id.

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 gives a clear usage guardrail: 'Call this only when the user asks,' which prevents autonomous removal. It does not name alternatives or describe when not to use it beyond the user-intent condition, so it is clear but not exhaustive.

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.