Skip to main content
Glama
Sign In

Valmera — AI Video Editor

by io.valmera
OverviewDiscussionsAdmin

Remove punctuation

remove_punctuation
Idempotent

Removes identified accent, strobe, junction or matte-flash items, or all punctuation items.

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_punctuation"
  }
}

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

C2.8/5.0
Behavior3/5

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

Annotations already declare mutability, idempotency and non-destructiveness, so the safety profile is covered. The description adds the meaningful behavioral fact of a bulk 'all punctuation items' mode, but omits whether that mode ignores the required ids, whether removal is reversible, and what happens to already-removed items.

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 sentence is efficient and front-loaded, but the enumeration is dense with internal jargon and the sentence is doing two different jobs (typed removal vs. bulk removal) without structure to separate them.

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?

With no output schema and a required parameters pair, the description must carry the burden of explaining what items are eligible for removal and how the bulk mode is invoked; it does neither. An agent cannot reliably construct a call from name, schema and this sentence alone.

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 50%: project_id is documented, but ids (array-or-string of strings) has no schema description and none in the description either. Critically, the description never explains how the 'all punctuation items' mode interacts with the required ids parameter, leaving the main calling decision undocumented.

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?

The description states a specific verb plus an enumerated set of resources ('accent, strobe, junction or matte-flash items'), which tells an agent this is not text-punctuation removal and separates it from siblings like remove_text or remove_stylize. The term 'punctuation items' itself is never defined, so the purpose is clear in effect but rests on unexplained jargon.

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 statement of when to use this tool versus the many sibling removers (remove_aspect_shift, remove_stylize, remove_motion_graphic, etc.) or versus add_accent/add_strobe. The 'or all punctuation items' alternative is mentioned but without the condition that selects it.

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