mib2c-mcp

Overview Schema Source Related Servers Discussions Admin

Move points or touch areas

move_items

Moves ambient light, climate, and car status items on the interior page, keeping them inside the picture with one undo step; use dx/dy to shift all or x/y to place one item.

Instructions

Moves zone file items on the interior page shown (ambient light, climate, car status), kept inside the picture; one undo step. Either dx / dy (move all items together) or x / y (place one item: a point by its top-left, a touch area by its bounding box top-left, a corner exactly). Unsaved until save.

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": {
      "items": "<items>"
    },
    "name": "move_items"
  }
}

Input Schema

Name	Required	Description	Default
`x`	No
`y`	No
`dx`	No
`dy`	No
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that items are clamped 'inside the picture', that the operation costs 'one undo step', and that changes are 'unsaved until save'. It omits error/edge behavior (unknown point or zone id) and whether partial application occurs, so it falls short of fully transparent.

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?

A single dense paragraph with the core action and constraints front-loaded; nearly every clause carries information. The clause about point/zone/corner anchoring is somewhat run-on and could be split for faster scanning.

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 covers the essentials: coordinate modes, clamping, undo granularity, and the need to call save. Missing only coordinate units and failure semantics, which an agent would need for fully confident invocation.

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?

Top-level schema coverage is 0%, so the description must compensate, and it does: it explains the exclusive dx/dy versus x/y modes and that x/y refers to a point's top-left, a touch area's bounding-box top-left, or a corner exactly. Units for dx/dy (pixels versus scene units) are never stated, leaving one meaningful gap.

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?

States a specific verb and resource: 'Moves zone file items on the interior page shown (ambient light, climate, car status)'. The page scoping implicitly separates it from siblings like move_parking and move_energy, but it never names align_items, distribute_items, or set_points, which also mutate the same items.

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?

The description gives mode-selection guidance: use dx/dy to move all items together, or x/y to place a single item. It does not say when to prefer this over align_items, distribute_items, or set_points, nor what preconditions (e.g. items must already exist in the zone file) are required.

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