Skip to main content
Glama

batch_convert

Convert multiple files at once with shared settings by specifying input paths, an output directory, and a target format for local batch processing.

Instructions

Convert multiple files at once with the same settings

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": {
      "inputPaths": "<inputPaths>",
      "outputDir": "<outputDir>",
      "outputFormat": "<outputFormat>"
    },
    "name": "batch_convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoFormat-specific options (same as individual converters)
outputDirYesDirectory for all output files
inputPathsYesArray of absolute input file paths
outputFormatYesTarget format extension e.g. 'wav', 'webp', 'json', 'csv'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden for a write operation that produces files in an output directory. It discloses only that all files share one settings set; it says nothing about what happens on partial failure, whether existing output is overwritten, ordering, or size/rate limits.

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 zero filler, and the batch/one-settings constraint is stated first. Brevity is not the problem here; the terseness reflects missing content rather than wasted words.

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?

For a batch mutation tool with nested options, no annotations, and no output schema, the description is too thin — partial-failure semantics, overwrite behavior, and the relationship to per-format converters are all absent. An agent could invoke it, but not predict its behavior on mixed or failing inputs.

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 description coverage is 100%, so all four parameters, including the nested options object, are documented in the schema itself; baseline 3 applies. The description adds only the "same settings applied to all inputs" framing, which marginally reinforces the options 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?

"Convert multiple files at once with the same settings" names a specific verb (convert) and scope (multiple files, one settings set), which implicitly separates it from the single-format converters in the sibling list. It stops short of naming a sibling explicitly, but the batch framing is unambiguous.

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 phrase "with the same settings" implies when this tool is appropriate (many files, uniform options) versus per-file conversion, but there is no explicit when-to-use or when-not-to-use statement and no pointer to the individual convert_* tools or get_supported_formats. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.