Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Check speech

check_speech
Read-only

Analyzes speech audio across a program window of up to 60 seconds, including cuts between source spans. Reports audible words, untranscribed sounds, clipping, clicks and sound-safe boundary evidence.

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": {
      "start": "<start>",
      "end": "<end>",
      "project_id": "<project_id>"
    },
    "name": "check_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYes
startYes
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description does add real context beyond them: the 60-second window cap and the set of reported findings. It does not cover cost, latency, behavior when the window exceeds 60 seconds, or how results are scoped across cuts.

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?

A single dense sentence with the core action front-loaded and the 60-second limit and reported outputs following immediately. Every clause carries information; nothing is wasted or repeated from the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 usefully enumerates what is reported rather than the return structure, and the window limit is stated. For a three-parameter read-only probe this is nearly sufficient, though result shape and behavior past the 60-second cap remain unaddressed.

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%: start and end are bare numbers with no descriptions, while project_id is documented. The description partially compensates by framing start/end as a program window capped at 60 seconds, but it never says whether these are seconds, frames, or timeline positions, leaving a meaningful gap the schema does not fill.

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 (analyzes) and resource (speech audio) scoped to a program window of up to 60 seconds, plus the exact findings it surfaces (words, untranscribed sounds, clipping, clicks, boundary evidence). That makes it distinguishable from analysis-adjacent siblings like get_audio_analysis or audit_audio_mix, though it never names them explicitly.

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 when-to-use guidance and no mention of alternatives such as audit_audio_mix, get_audio_analysis, or search_transcript. The phrase about cuts between source spans hints at the domain but does not tell an agent which situation should select this tool over those siblings.

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