WebP Batch Converter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_to_webpA | Batch convert images (PNG, JPG, JPEG) to WebP format with customizable options. Recursively scans directories and provides detailed conversion reports. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as batch converting images to WebP format, making it impossible for an agent to misselect among multiple options.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'convert_to_webp' follows a clear verb_noun pattern, and with no other tools to compare, there are no inconsistencies or deviations in naming conventions.
A single tool is generally too few for a server's purpose, as it limits functionality and can feel thin. For a batch conversion tool, additional operations like listing files, checking formats, or managing settings might be expected to provide a more complete surface, making the count borderline inadequate.
The tool covers the core conversion functionality well, but there are notable gaps in the surface. For a batch conversion domain, missing operations might include checking image formats, listing files before conversion, or providing status updates, which could lead to agent workarounds or inefficiencies in handling the workflow.