Skip to main content
Glama

x402image

by org.x402image

process

Apply an ordered pipeline of image ops in a single paid call: one payment, one output. Price is the sum of the included ops’ prices — call without payment to get a 402 quote. Input: source (image URL), steps (ordered [{op, params}], e.g. [{"op":"remove_background"},{"op":"resize","params":{"width":800}}]). Call service_info for the available ops and their per-op prices. Output: the processed image as a short-lived signed URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stepsYesOrdered ops to apply in a single pass.
sourceYesPublic https:// URL of the source image to process.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Discloses payment requirement, pricing model, error response (402 quote), and output format (short-lived signed URL), adding significant value beyond minimal annotations.

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?

Concise yet comprehensive; every sentence adds unique value. Front-loaded with purpose and cost, then input format, then references to service_info, then output.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, description adequately explains output and error handling. References sibling tools for further info, making it self-contained for its complexity.

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 already covers 100% of parameters; description adds concrete example and structure for 'steps' array, enhancing understanding beyond schema definitions.

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?

Clearly states the tool applies an ordered pipeline of image ops in a single paid call, distinguishing it from sibling atomic tools like resize or remove_background.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear context for use (combining multiple ops in one payment) and references service_info for available ops and pricing. Missing explicit when-not-to-use, but implied.

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

All x402image toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool targets a distinct operation: optimization, pipeline processing, background removal, resizing, upscaling, and service discovery. No two tools overlap in purpose.

Naming Consistency5/5

All tool names follow the consistent verb_noun pattern in lowercase snake_case (optimize, process, remove_background, resize, service_info, upscale).

Tool Count5/5

With 6 tools, the server is well-scoped for an image processing service. Each tool earns its place, covering core operations, a pipeline composer, and metadata discovery.

Completeness4/5

The tool set directly offers essential transformations (compress, resize, background removal, upscale) and a pipeline tool (process) that can invoke additional ops via API, covering most common workflows. Missing direct tools for rotation or filters are minor gaps.

Resources