Skip to main content
Glama

WEBP в JPG

webp_to_jpg

Конвертирует WEBP в JPG. Одна картинка — JPG, несколько — ZIP. file_urls: публичные URL картинок WEBP.

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": {
      "file_urls": "<file_urls>"
    },
    "name": "webp_to_jpg"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare non-destructive, open-world, non-idempotent behavior. The description adds meaningful behavior beyond that: one image produces JPG while multiple images produce ZIP, and inputs are public WEBP URLs. It does not discuss limits or failure behavior, but the output schema likely covers returns.

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?

The description is two short sentences with no wasted wording. The conversion purpose is front-loaded, followed by the important output variation and a compact parameter note.

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?

For a one-parameter converter with annotations and an output schema, the description covers the core purpose, output behavior, and parameter meaning. It omits edge cases such as maximum file count or size and does not route the agent to sibling converters, but the essential information is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the schema only says file_urls is an array of strings. The description meaningfully clarifies that these are public URLs of WEBP images, though it leaves array length and URL validation implicit.

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 states a specific verb and resource: converts WEBP to JPG. It also clarifies the output shape for one versus multiple images, so an agent can distinguish this converter from sibling converters such as png_to_jpg or heic_to_jpg.

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 implied by the purpose: use this tool for WEBP images that should become JPG. However, it does not explicitly say when to choose it over sibling tools or mention exclusions, prerequisites, or alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.