Skip to main content
Glama
Sign In

Montik

by app.montik
OverviewDiscussionsAdmin

Duplicate clip

duplicate_clip

Duplicate a clip (placed right after it unless start is given).

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": {
      "clipId": "<clipId>"
    },
    "name": "duplicate_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
clipIdYes
projectIdNoProject to act on (default: the open one)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, non-open-world operation. The description adds useful placement behavior, but it does not disclose whether effects, keyframes, or other clip attributes are duplicated, nor what the operation returns.

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?

The description is a single efficient sentence with the core action front-loaded and the placement condition clearly parenthesized. There is no unnecessary wording.

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 simple three-parameter duplication tool with no output schema, the description covers the core action and placement behavior. However, it leaves gaps around when to choose this over sibling tools and does not clarify the start parameter's format.

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?

Schema coverage is only 33%, with projectId documented in the schema. The description adds meaning for the start parameter by saying the duplicate is placed right after the original unless start is given, but it does not explain the expected format or units for start.

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 states a specific verb and resource: 'Duplicate a clip.' It also clarifies placement behavior, which helps distinguish it from add_clip and paste_clips, though it does not explicitly name those alternatives.

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?

The description explains what the tool does but gives no guidance on when to use it versus alternatives such as add_clip, paste_clips, or split_clip. The placement note is useful but is not usage guidance.

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

All Montik toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources