mib2c-mcp

by TomasSlekys

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Get image

get_image

Read-only

Retrieve one skin image as PNG, choosing the stored current version or its unsaved replacement when one exists.

Instructions

One image from the skin as PNG: as stored ("current") or its unsaved replacement ("new", the default when there is one).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_image"
  }
}

Input Schema

Name	Required	Description
`path`	No	Or a path from images.res, e.g. "0203070200/GenericCarAdjuster/AmbianceLight/Interior_LHD.png"
`index`	No	The image index in images.mcf
`which`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

A3.7/5.0

Behavior4/5

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

The readOnlyHint=true annotation is consistent with fetching an image. Beyond annotations, the description discloses that the response is a PNG and that it may reflect either the stored file or an unsaved replacement, which is meaningful context an agent cannot get from the schema. It does not explain error behavior for a bad path or index, keeping it below 5.

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?

A single front-loaded sentence that packs resource, format, both modes, and the default rule with no filler. The parenthetical is dense but each clause carries information.

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?

With three optional parameters and no output schema, the description usefully compensates by naming the return type (PNG) and the variant semantics. What is missing is how path and index interact when both or neither are supplied, and what happens on lookup failure.

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 67% and the schema documents path and index on its own. The description adds genuine meaning for "which" by mapping current/new to stored vs unsaved and stating that "new" is the default when one exists, which the bare enum does not convey. The path vs index relationship remains unclarified.

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?

The description states a specific verb and resource (fetch one image from the skin) and names the output format (PNG), plus the two selectable variants. It does not distinguish itself from siblings such as export_image, list_images, or get_preview, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of alternatives like export_image (which presumably writes the PNG somewhere) or list_images (which enumerates them). The only usage-ish information is the default resolution for "which", which is parameter semantics rather than invocation guidance.

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