Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Audit captions

audit_captions

Compiles and audits the current caption artifact used by rendering. Reports coverage, lateness, overlaps, density, line wrapping and other measured caption issues, including speech represented by graphics.

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": "audit_captions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
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

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, which implies the 'compile' step persists something, yet the description never says what is created or changed, nor whether it is safe to run repeatedly (idempotentHint=false). It does add real value beyond the annotations by detailing the report's contents, which matters since there is no output schema.

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?

Two sentences with purpose front-loaded and the measurement list following. The trailing phrase 'and other measured caption issues, including speech represented by graphics' is slightly loose but conveys a meaningful scope boundary, so almost nothing is wasted.

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?

With no output schema, the description does a fair job sketching what the audit reports, but it omits pagination behavior, result size expectations, and what 'compiles' produces. For a tool with an unexplained write-like side effect and two undocumented parameters, an agent is left with real gaps.

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 coverage is only 33%: project_id is documented in the schema, but limit and offset are undocumented in both the schema and the description. The description says nothing about pagination or how the audit is scoped, so it fails to compensate for the coverage gap.

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

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb pair and resource ('Compiles and audits the current caption artifact used by rendering') and enumerates what is measured (coverage, lateness, overlaps, density, line wrapping). This clearly separates it from sibling audits like audit_audio_mix and audit_motion, which target different artifacts.

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?

Usage is only implied by 'used by rendering' — an agent can infer this belongs before a render or before applying caption fixes, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. check_speech, set_caption_fixes). Nothing tells the agent whether this is a prerequisite step or a standalone inspection.

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