Skip to main content
Glama

video_to_gif

Read-onlyIdempotent

Convert a video to an animated GIF -- two-pass palette encoding

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": {
      "fileBase64": "<fileBase64>"
    },
    "name": "video_to_gif"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileBase64YesThe input file as a base64 string, without a data: prefix.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / fileBase64 / description
      Added value: +"The input file as a base64 string, without a data: prefix."
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile requires no elaboration. The description adds only that two-pass palette encoding is used, a processing detail rather than operational context: it says nothing about size limits, encoding duration, or what happens with large base64 payloads. Given that the annotations carry the safety profile, this is adequate but not rich.

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 tightly front-loaded sentence with no padding: the action is stated before the technical detail. It is efficient, though its density is low for an operation that converts one binary format into another.

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

Completeness3/5

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

For a one-parameter tool with full schema coverage, the definition covers the essentials. However, since no output schema exists, the description could have stated what is returned (e.g. base64 GIF or a link) and any format constraints. It is minimally adequate.

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

Parameters3/5

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

There is a single required parameter, fileBase64, and the schema documents it fully as base64-encoded input without a data: prefix (100% coverage). The description adds no further parameter meaning, but baseline 3 is appropriate when the schema does the work.

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 concrete verb and resource: convert a video into an animated GIF. The palette-encoding note reinforces what it produces. It does not distinguish itself from the sibling video_convert, so an agent must infer that this tool is the GIF-specific special case.

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 when-to-use guidance, no exclusions, and no reference to alternatives such as video_convert for other target formats. The agent must reason about tool selection on its own, based only on the name and a vague phrase.

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.

Resources