Skip to main content
Glama
Sign In
mib2c-mcp

mib2c-mcp

by TomasSlekys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Copy points to another side or car

copy_points

Copies interior point and touch-area positions from one car side to another in a single undo step, mirroring driving sides or scaling to differently sized images.

Instructions

Copies the interior page's point and touch area positions from one car / side to another, in one undo step in the target file: points by id, touch areas by order. Between driving sides they are mirrored (by default); to a picture of another size they are scaled (by default). Default: from the car and side shown, to the other side of the same car.

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": "copy_points"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
whatNo
scaleNo
mirrorNo
pointsNoOnly these point ids

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

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 full burden and does well: it discloses atomicity ('in one undo step in the target file'), the matching semantics ('points by id, touch areas by order'), and the defaults for mirroring between driving sides and scaling to a differently sized picture. It does not say whether existing target data is overwritten or what the tool returns.

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 action and default scope, then the behavioral rules. The colon-and-list punctuation is efficient; nothing is padding, though the phrasing is compressed enough that 'zones' versus 'touch areas' takes rereading.

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?

For a six-parameter, all-optional, nested-object tool with no annotations and no output schema, the description covers most behavioral ground but leaves the 'what' selector and overwrite semantics unaddressed, and says nothing about the result of the copy. Adequate, not complete.

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 only 17% (just the two nested 'car' fields), so the description must compensate, and it partially does: it explains that 'points' filters by id, that 'mirror' and 'scale' default to true, and what 'from'/'to' default to. It never explains the 'what' enum (all/points/zones) or clarifies how 'zones' relates to the 'touch areas' it mentions, leaving a gap.

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 ('Copies the interior page's point and touch area positions from one car / side to another') and scopes it to interior-page data, which separates it from set_points, move_items, and align_items among the siblings. An agent can tell what it does without opening the schema.

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 default sentence ('from the car and side shown, to the other side of the same car') gives useful invocation context, and the mirror/scale rules hint at the two main scenarios. However, there is no explicit when-to-use versus set_points or move_items, and no stated preconditions or exclusions.

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