Skip to main content
Glama

generate_device_mockup

Frame a real screenshot with an animated device border to produce a device mockup without downloading stock device assets.

Instructions

Frame an actual screenshot with an animated device border; no stock device download.

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": {
      "timeline": "<timeline>",
      "shotIndex": "<shotIndex>",
      "output": "<output>"
    },
    "name": "generate_device_mockup"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
timelineYes
shotIndexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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?

Annotations declare the write profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false), so safety is covered. The description adds little beyond that: it doesn't say what artifact is produced (video, image, animated render), what 'animated border' entails, why 'timeline' and 'shotIndex' are required inputs, or what the 0-29 index range implies about the surrounding project.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded clause with no filler sentences, so length is fine. But the available space is spent on a marketing-style qualifier ('no stock device download') rather than on the parameter or behavioral detail an agent actually needs.

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?

With three opaque required parameters, zero schema documentation, and an output schema that can cover return values, the description still needed to explain the inputs and the generated artifact. It covers neither, so an agent would be guessing before every call.

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

Parameters1/5

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

Schema description coverage is 0% across three required parameters (timeline, shotIndex, output), and the description supplies no meaning for any of them. An agent cannot tell whether 'timeline' is a path, an ID, or an inline JSON structure, nor what 'output' expects.

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?

The description names a specific verb and resource ('Frame an actual screenshot') and adds a distinguishing qualifier: an animated device border built from the real screenshot rather than a stock device asset. An agent can see the tool's job at a glance, though it never names or rules out any sibling generator.

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 only an implicit steer ('no stock device download'), which hints you should pick this over downloading device assets, but no explicit when-to-use, when-not-to-use, or named alternative among the many generate_* siblings such as generate_3d_scene or generate_storyboard.

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