mib2c-mcp

Overview Schema Source Related Servers Discussions Admin

Replace image

replace_image

Replaces a selected MIB2 skin image with a local PNG, JPEG, or WebP file, matching its size or applying fit modes; shared images update everywhere and stay unsaved until saved.

Instructions

Replaces one image of the skin with a picture file on this computer (PNG, JPEG or WebP), stored in the image's format. It must have the image's size (only ambient feature images may change size) unless fit is "fit", "fill" or "stretch". A shared image changes everywhere it is used. Unsaved until save; revert_image takes it back.

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": "<file>"
    },
    "name": "replace_image"
  }
}

Input Schema

Name	Required	Description
`fit`	No	exact (default): as it is; fit: whole picture inside; fill: cover, cropping; stretch: distort to the size
`file`	Yes	Path of the picture file on this computer
`path`	No	Or a path from images.res, e.g. "0203070200/GenericCarAdjuster/AmbianceLight/Interior_LHD.png"
`index`	No	The image index in images.mcf

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: accepted formats, the size-matching requirement with the fit exceptions and the ambient-feature carve-out, the fact that a shared image changes everywhere, and that the edit is unsaved until save. It doesn't cover permissions, validation failures, or the response, which keeps it off a 5.

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 only four tight sentences, each carrying distinct information (format, size rule, sharing, undo state). The size/fit sentence is dense and would read more easily split, but no sentence is filler.

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 mutation tool with no annotations and no output schema, the description supplies the critical semantics an agent needs: format limits, size constraint, shared-image side effects, and the unsaved/undo model. Failure modes and required preconditions (e.g., an existing target image) remain unstated.

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, but the description adds real meaning: it restricts file to PNG/JPEG/WebP (absent from the schema) and explains how the size rule is relaxed when fit is "fit", "fill" or "stretch", tying the enum to observable behavior. It doesn't explain path vs file precedence or what index does beyond the schema's own wording.

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: "Replaces one image of the skin with a picture file on this computer". The singular "one image" implicitly distinguishes it from the sibling replace_images, and the mention of revert_image clarifies what it is not.

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?

Makes clear when to use it (single image swap) and points to revert_image as the undo path, plus notes the change is "Unsaved until save". It stops short of explicitly contrasting with replace_images for batch replacement, leaving that to inference from the plural sibling name.

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