Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Remove overlay

remove_overlay
Idempotent

Removes an identified visual overlay.

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": {
      "id": "<id>",
      "project_id": "<project_id>"
    },
    "name": "remove_overlay"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
project_idYesExplicit project identifier for this request. The connection's navigation pointer does not select the target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / project_id / description
      Previous value: -"Required immutable scope for this call. Copy the id from list_projects/open_project/project_state; the active-project pointer is never used to guess."New value: +"Explicit project identifier for this request. The connection's navigation pointer does not select the target."
  2. First observed

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false; the description adds nothing about what removing an overlay does to the project, whether it is undoable, or what happens on an unknown id. Notably it does not reconcile the tension between a "remove" verb and destructiveHint=false, which an agent might want explained.

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?

A single short sentence with no wasted words, but it is terse to the point of under-specification rather than efficiently informative. There is nothing front-loaded beyond the bare action.

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?

For a mutation tool with an undocumented required identifier and no output schema, the description leaves significant gaps: what an overlay id is, whether removal is reversible, and what state the project ends in. Annotations cover the safety profile, but the identifier semantics remain unexplained.

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 50%: project_id is well documented, but the required `id` parameter has no description at all. The phrase "identified visual overlay" faintly implies the id refers to an overlay, but the description never confirms this or states whether the id is scoped to the project.

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 ("Removes") and a specific resource ("an identified visual overlay"), so an agent can distinguish it from add_overlay or set_overlay_motion. It stops short of distinguishing it from the wider family of removal siblings, but the resource noun does most of that work.

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 guidance on when to use this versus alternatives such as remove_stylize, remove_ui_scene, or move_overlay, nor any prerequisite or sequencing information. The agent must infer everything from the name alone.

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

All Valmera — AI Video Editor 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