Skip to main content
Glama

export_video

Validates the complete video stream before copying a local MP4 artifact, ensuring exports use checked video data.

Instructions

Validate the complete video stream before copying a local MP4 artifact.

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": {
      "input": "<input>",
      "output": "<output>"
    },
    "name": "export_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
outputYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write profile is partly covered. The description adds a genuinely useful behavioral trait beyond that: the stream is validated first and only then is the artifact copied, implying a possible validation failure path. It stops short of disclosing what happens to an existing output file, whether the copy is atomic, or how failures surface.

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?

A single front-loaded sentence with no filler; the validation-then-copy ordering is stated up front. Its brevity is efficient rather than padded, though the same brevity is what leaves the parameters and alternatives unaddressed.

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?

An output schema exists, so return values need no explanation, but this is a non-read-only file-producing operation with two completely undocumented parameters and no stated constraints on overwriting the destination. Relative to the tool's complexity and mutation semantics, the definition leaves material gaps.

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 both required parameters, so the description must carry the burden and largely does not. It only hints that one path is a 'local MP4 artifact' source; which of input or output is source vs destination, acceptable formats, and whether the output may exist are all left unspecified.

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 names two concrete actions (validate a video stream, copy a local MP4 artifact), which is more specific than the bare name export_video. However, it never clarifies how 'export' relates to 'copy' or how this differs from adjacent siblings such as validate_export or render_video, leaving an agent to guess the boundary.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The only usage signal is the implied ordering 'validate ... before copying', which tells the agent sequencing but not when this tool should be chosen at all.

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