Skip to main content
Glama

video_reply

Displays a short message in the studio chat so users can receive status updates or prompts while refining video scenes.

Instructions

Show a short message to the user in the studio chat.

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": {
      "text": "<text>"
    },
    "name": "video_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden. It does not say whether the message is ephemeral or persisted in a transcript, whether it interrupts or blocks the user, what length counts as "short," or whether an active studio session is required. Only the mild hint of brevity is offered.

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?

One short sentence, front-loaded with the action and destination, with no filler. It is efficient, though the efficiency comes partly from omitting needed detail.

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

Completeness2/5

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

For a one-parameter tool this could be sufficient, but with no annotations, no output schema, no parameter documentation, and a name/description mismatch about whether it is a reply or a broadcast, the definition leaves key gaps an agent would need resolved before calling it confidently.

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

Parameters2/5

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

Schema description coverage is 0% for the single required "text" parameter, so the description must compensate. It only implies a brevity constraint via "short message," with no character limit, formatting rules, or accepted content — far short of what a 0%-coverage parameter needs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and destination ("show a short message to the user in the studio chat"), so an agent understands it emits text into the studio chat. However, the name "video_reply" implies answering a prior prompt, while the description describes a generic message display; that mismatch leaves the actual purpose (a reply to a prompt vs. an arbitrary broadcast) ambiguous relative to siblings like video_wait_for_prompt.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus alternatives such as video_wait_for_prompt or video_studio, nor any preconditions such as needing an active session or a pending prompt. The agent must infer the usage context entirely from the tool name.

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