Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Apply format pack

apply_format_pack

Applies an explicitly selected format pack's craft brief and chosen proposals in one batch. Depending on the pack and arguments, it may return proposals for selection instead. Existing framing is preserved unless aspect changes are explicitly enabled.

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

Input Schema

NameRequiredDescriptionDefault
packNo
picksNo
aspectNo
intensityNo
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. Changed2 schema fields changed
    • addedInput schema / properties / aspect
      Added value: +{
+  "type": "boolean"
+}
    • changedInput schema / properties / pack / enum
      Previous value: -[
-  "auto",
-  "A",
-  "B",
-  "C",
-  "D",
-  "H",
-  "none"
-]New value: +[
+  "auto",
+  "A",
+  "B",
+  "C",
+  "D",
+  "E",
+  "F",
+  "G",
+  "H",
+  "I",
+  "J",
+  "none"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / pack / enum
      Previous value: -[
-  "auto",
-  "A",
-  "B",
-  "C",
-  "H",
-  "none"
-]New value: +[
+  "auto",
+  "A",
+  "B",
+  "C",
+  "D",
+  "H",
+  "none"
+]
  4. Added

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already establish the safety profile (not read-only, not destructive, not idempotent), so the description adds real value beyond them: it discloses the dual-mode outcome (applying versus returning proposals for selection) and the framing-preservation rule that aspect flagging can override. It does not explain the consequences of a non-idempotent batch run or any permission requirements, which keeps it below a 5.

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?

Three tight sentences with no filler, and the core 'applies ... in one batch' clause is front-loaded. The dual-mode caveat follows in the right place, though the phrasing is slightly dense with undefined internal terms.

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 five-parameter mutation tool with no output schema and 20% schema coverage, the description covers the batch behavior and the framing-preservation caveat, which is the most important thing. It still leaves the agent guessing about what a 'format pack' enumerant means, what intensity changes, and what the returned proposals look like when the tool chooses not to apply.

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 20%, so the description carries real weight, and it does map several parameters to meaning: pack must be 'explicitly selected', picks correspond to 'chosen proposals', and the aspect flag corresponds to 'aspect changes are explicitly enabled'. It says nothing about the intensity values (calm/designed/charged) or the twelve pack enum options, leaving a substantial gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/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 ('applies ... format pack's craft brief and chosen proposals in one batch'), so the basic operation is identifiable. However, 'craft brief' and 'chosen proposals' are internal jargon, and nothing distinguishes this from nearby siblings such as apply_look or apply_recipe, which an agent could easily confuse it with.

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 explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. The statement that it 'may return proposals for selection instead' describes an outcome rather than telling the agent under what conditions it should choose this tool over apply_look or apply_recipe.

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