Skip to main content
Glama

gif

Converts a demo project’s final MP4 into a README-ready animated image, returns a job ID to poll, and blocks overlapping jobs.

Instructions

Convert output/final-demo.mp4 to a README-ready GIF. Returns a jobId immediately — poll job_status. Rejects if another job is running.

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": {
      "dir": "<dir>"
    },
    "name": "gif"
  }
}

Input Schema

NameRequiredDescriptionDefault
dirYesdemo project directory — pass an absolute path
fpsNo
outNo
widthNo

Output Schema

NameRequiredDescriptionDefault
kindYes
jobIdYes
statusYes
demoDirYesresolved absolute demo directory
logFileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.20.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / fps / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / width / maximum
      Added value: +9007199254740991
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observedv0.9.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the key async trait (returns a jobId immediately) plus a concurrency limit (one job at a time). It says nothing about where the GIF is written, whether existing files are overwritten, or what a rejection looks like, so the mutation surface is only partially exposed.

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?

Three short, front-loaded sentences with zero filler: what it does, what it returns, and what blocks it. Every sentence carries an actionable fact.

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?

An output schema exists, so return values needn't be explained, and the async/polling contract is covered. However, three of four parameters (fps, out, width) are undocumented in both schema and description, leaving gaps for a conversion tool with multiple knobs.

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 only 25% — just `dir` is documented — and the description adds no meaning for `fps`, `out`, or `width`. It also references a source file path that isn't a parameter, which can mislead an agent about what to pass.

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 (convert an mp4 to a README-ready GIF) and the target artifact, which lets an agent distinguish it from sibling media tools like stills, frames, and render. Minor friction: it names a hardcoded source file (output/final-demo.mp4) while the schema takes a project `dir`, so the implied input is not quite what the tool actually accepts.

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

Usage Guidelines3/5

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

Routes the agent correctly after invocation ('poll job_status') and states a precondition (rejects if another job is running), which is useful. It gives no guidance on when to choose GIF over siblings such as stills, frames, or embed, so alternative selection remains inferred.

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