Skip to main content
Glama

open_player

Read-onlyIdempotent

Open a video in the chat for a playback URL.

Pass a URL from `list_jobs` or `get_job_status_detailed`. When the
result includes `client_note`, tell the user that sentence. Do not
transcode only to force playback.

Read `qencode://docs/player` before calling. It says which URLs play
and what to do when they do not.

Args:
    source_url: https playback URL from `list_jobs` or
        `get_job_status_detailed`.
    poster_url: optional https image shown before playback.
    source_type: optional MIME type, such as "video/mp4". The player
        infers one when this is omitted.
    title: optional title shown on the player.

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": {
      "source_url": "<source_url>"
    },
    "name": "open_player"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
poster_urlNo
source_urlYes
source_typeNo

Output Schema

NameRequiredDescriptionDefault
titleNo
poster_urlNo
source_urlYes
client_noteNo
license_keyNo
source_typeNo
prefer_nested_embedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds real behavior beyond that: results may include a `client_note` that must be surfaced, some URLs may not play, and transcoding should not be forced purely for playback. It stops short of describing failure modes or pagination/format details, which the docs pointer partly offloads.

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?

Front-loaded with purpose, then guidance, then a parameter block — a logical order with little filler. `source_url` is described twice (body and Args), a minor redundancy, though it reflects docstring convention.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read-only tool with an output schema and full annotations, everything an agent needs to call it correctly is present: input provenance, prerequisites, per-parameter meaning, and post-call behavior. Return values are rightly left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does: `source_url` must be an https playback URL from specific sibling tools, `poster_url` is an optional pre-playback image, `source_type` is an optional MIME type with documented inference when omitted, and `title` is display text. That is meaning well beyond the schema's bare types and defaults.

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?

States a specific verb and resource ("Open a video in the chat for a playback URL"), which distinguishes it from siblings like transcode_video or get_download_url. The phrase "in the chat" is slightly ambiguous about where the player renders, keeping it short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the source of valid input (URLs from `list_jobs` or `get_job_status_detailed`), states a prerequisite ("Read `qencode://docs/player` before calling"), and gives a negative rule ("Do not transcode only to force playback"). It also routes post-call behavior (relay `client_note` to the user), so both when-to-use and when-not are covered.

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.