Skip to main content
Glama
Sign In

Panda Video

by com.pandavideo
OverviewDiscussionsAdmin

Update Sign Language Display

panda_update_sign_language_display
DestructiveIdempotent

Change how the sign language interpreter (Libras) window shows on a video's player: start time, size, position, autostart, or a free position/size. Only fields passed are changed. The interpreter clip itself is uploaded and removed on the dashboard (Video → Settings → Libras); this tool does not create or delete it. Choosing a preset size or position drops the free position (custom), like the dashboard. Returns the updated sign language entry.

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": {
      "video_id": "<video_id>"
    },
    "name": "panda_update_sign_language_display"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoPreset window size
customNoFree position and size (fractions of the player, 0–1); overrides size/position
languageNoSign language, by the country's language code ('pt-br' = Libras); needed only if the video has more than one
positionNoPreset window corner
video_idYesVideo ID (the main video, not the interpreter clip)
autostartNotrue = interpreter already on when the video starts
start_timeNoSecond of the video when the window appears

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: partial-update semantics, the precedence rule where choosing a preset size/position silently drops the custom geometry (this is what makes the destructiveHint meaningful), and that the updated entry is returned. It does not cover failure modes, e.g. what happens when the video has no interpreter or when `language` matches nothing, so it falls short of a full behavioral account.

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?

Four tight sentences led by the core action, then the mutation rule, then the out-of-scope boundary, then the preset/custom interaction. No filler and no repetition of schema content such as enum values.

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 nested, 7-parameter mutation tool with no output schema, the description covers the action, mutation semantics, side effects, out-of-band prerequisites, and states what is returned. An agent has everything needed to decide and invoke; field-level detail is fully carried by the schema.

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 the baseline is 3, but the description adds cross-parameter interaction the schema states only in one direction: picking a preset `size`/`position` clears `custom`, mirroring the dashboard. That is genuine semantic value for the flat mechanics of a 7-parameter tool; the remaining parameters are left entirely to the schema.

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?

States a specific verb (change) and resource (the Libras/sign-language interpreter window on a video player) and enumerates the mutable facets: start time, size, position, autostart, custom geometry. It also draws an explicit boundary — the interpreter clip itself is uploaded/removed on the dashboard, not here — which separates it from the sibling upload/delete tools.

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?

Gives positive usage ('change how the window shows'), a partial-update rule ('Only fields passed are changed'), and an explicit exclusion with a pointer to where the excluded work is done ('uploaded and removed on the dashboard: Video → Settings → Libras'). That is when-to-use plus when-not-to-use plus the alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Panda Video toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources