Skip to main content
Glama

ai_modeling_image_process

Process an existing image by generating multiviews, splitting, upscaling, or regenerating it with a stable request_id that reuses jobs and prevents unsafe retries.

Instructions

generate multiviews, split, upscale or regenerate an existing image. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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": {
      "request_id": "<request_id>",
      "max_estimated_credits": "<max_estimated_credits>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_image_process"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes
max_estimated_creditsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, destructive=false) by disclosing that it consumes Studio account credits, that request_id makes calls idempotent, that reuse returns the original job, and that changed inputs produce a conflict. The only gap is that it never states what an outcome_unknown response looks like or how to resolve it.

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?

Three dense sentences, front-loaded with the capabilities and followed by the account/idempotency contract. Slightly telegraphic ('generate multiviews, split, upscale') but no filler.

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

Completeness3/5

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

The idempotency contract is the most important thing an agent needs for a credit-consuming, non-idempotent-looking operation, and it is present. But with 0% schema coverage, a nested parameters object, and no output schema, the definition leaves the credit cap, input selection, and result shape unexplained.

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 0%, so the description must carry parameter meaning. It adds strong semantics for request_id (stable key, replay returns original job, conflicting input fails), but says nothing about max_estimated_credits, the asset_id vs image_path distinction, or how each action maps to those inputs.

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?

Names specific verbs (multiview, split, upscale, regenerate) tied to the image resource and scopes it to 'an existing image', which implicitly separates it from the sibling generate tool. It does not explicitly name that alternative, and the fifth enum value (regenerate_multiview) is only loosely covered by 'multiviews'.

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?

Provides a real operational rule for retries ('outcome_unknown must never be blindly retried') and implies the idempotent-reuse pattern. However, there is no explicit statement of when to prefer this over ai_modeling_image_generate or ai_modeling_image_crop, so action selection against siblings is left to inference.

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

Deploy Server

Other Tools