Skip to main content
Glama

Edit Image

edit_image

Change one of the user's own HalalGen pictures with words, like the web Image Editor: 'make the sky a warm sunset', 'put the bottle on a marble table'. Pass the picture as image_id or a HalalGen link (other sites are refused) and the change as prompt. Faces already in the picture stay as they are; anyone added gets a smooth face. Default model WanPro on paid plans, CF_Flux2Dev on the free plan. Priced like one image of that model.

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": {
      "prompt": "<prompt>"
    },
    "name": "edit_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoEdit model: WanPro (best, paid), Qwen2Pro (fast, paid), Seedream40 (artistic, paid), CF_Flux2Dev (detailed, free plan too), CF_Flux2Klein (fast draft, free plan too).
promptYesWhat to change in the picture, in plain words. Avoid faces.
image_idNoImage or upload ID from list_generations, search_vault or an earlier tool result.
image_urlNoLink to the user's own picture on HalalGen (https://cdn.halalgen.ai/... or https://api.halalgen.ai/image/...), if you don't have the ID. Other links are refused.
is_privateNoKeep the result out of the public gallery. Needs a paid plan.
aspect_ratioNoShape of the result. Defaults to the picture's own shape; shapes a model can't make go to the nearest one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / is_private / description
      Previous value: -"Keep the result private in the user's Vault."New value: +"Keep the result out of the public gallery. Needs a paid plan."
  2. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already flag non-read-only, non-idempotent, open-world behavior, so the bar is lower. The description adds genuinely useful context: existing faces are preserved, added faces get smoothed, model defaults vary by plan, and each call is billed as one image of the chosen model. It does not mention rate limits, failure modes, or what happens to the source image, leaving it at a solid mid score.

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?

Front-loaded with the core action and examples, then a short block of constraint, model-default and pricing facts that each earn their place. Some sentences are dense run-ons ("Faces already in the picture stay as they are; anyone added gets a smooth face") but nothing is 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?

Covers input sourcing, model choice, plan constraints and cost for a moderately complex tool with no output schema. It never says what the call returns (image ID, URL, or inline result), which matters since a follow-up tool would need that identifier.

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 coverage is 100%, so the baseline is 3, and the description still adds value by tying image_id and link inputs together and clarifying that non-HalalGen URLs are rejected and that the default model depends on plan. The is_private and aspect_ratio semantics are left entirely to the schema.

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?

States a specific verb and resource ("Change one of the user's own HalalGen pictures with words") and scopes it to existing user images, which implicitly separates it from generate_image and upscale_image. Example prompts make the intended operation unmistakable.

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?

Explains when to use it (modifying an existing picture rather than creating one), how to supply the source (image_id or a HalalGen link; other sites refused), and which model to pick on paid vs free plans. It never names a sibling tool or explicitly rules out alternatives, so it stops short of full routing guidance.

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.

Resources