Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Remove world

remove_world
Idempotent

Removes identified world definitions and detaches graphics that refer to them, or detaches selected motion graphics directly.

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": {
      "ids": "<ids>",
      "project_id": "<project_id>"
    },
    "name": "remove_world"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
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. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description discloses the important side effect that dependent graphics are detached rather than deleted, which is exactly the context needed to reconcile a 'remove' tool with destructiveHint=false. It also reveals the dual-mode behavior. What it does not cover is what state the detached graphics end up in or what happens if an id is not found.

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?

A single front-loaded sentence with no filler; the removal target comes first and the side effect second. The trailing 'or' clause makes it slightly run-on but every clause carries distinct meaning.

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 two-parameter mutation with no output schema, the definition covers the main behavioral question (graphics are detached, not destroyed) but leaves return/error semantics and the id-type contract unstated. Adequate to call it, not quite enough to predict its results confidently.

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 50%: project_id is well documented in the schema, while ids is a bare string array. The description hints that ids may be world definitions or motion graphics depending on mode, but never says so explicitly or whether the two kinds can be mixed in one call, so it only partially compensates for the undocumented parameter.

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 ('Removes identified world definitions') and adds the cascade ('detaches graphics that refer to them'), so the agent knows exactly what is affected. It also names a second mode ('or detaches selected motion graphics directly'), but does not distinguish that mode from the sibling remove_motion_graphic, which is the one obvious ambiguity.

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?

The 'or' clause implies two invocation modes, so the agent can infer that ids may target worlds or graphics. However, there is no explicit guidance on which mode to choose, no preconditions (e.g. whether graphics must still be placed in the world), and no statement about when to prefer remove_motion_graphic instead.

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