mib2c-mcp

Overview Schema Source Related Servers Discussions Admin

Set preview situation

set_preview

Configure the simulated car preview by setting ambient light, climate, vehicle status, and active lights or vents without writing to the skin, then take a screenshot to review.

Instructions

Sets what the car reports in the preview (nothing is written to the skin): ambient light, climate, car status, and which ambient lights or climate vents are on (page shown). Take a screenshot after to see it.

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

Input Schema

Name	Required	Description
`points`	No	Ambient light and climate pages: switch lights / vents by point id
`status`	No
`ambient`	No
`climate`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Nov 7, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the most important trait: the operation is preview-only and does not modify the skin file. However, it says nothing about whether it is reversible, whether it requires a car to be selected first, or – critically for a tool with zero required parameters – whether omitted fields are left untouched or cleared.

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 single sentence plus one short actionable follow-up, with no padding. The trailing '(page shown)' is cryptic and the phrase listing lights/vents is slightly tangled, but overall it is tight.

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 tool with four nested, all-optional objects, no annotations and no output schema, the description covers what the tool controls and what to do next but omits partial-update semantics, defaults, and any prerequisite (selecting a car / message ids). Adequate orientation, incomplete for correct invocation in edge cases.

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?

The description names the four semantic domains, which is useful given only 25% schema description coverage, mapping roughly onto ambient, climate, status and points. It adds no field-level meaning beyond the schema, though, and leaves the merge-vs-replace question for nested objects (e.g. partially specified ambient or climate blocks) unresolved in the description itself.

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 ('Sets what the car reports in the preview') and enumerates the four domains it governs (ambient light, climate, car status, active lights/vents), which maps cleanly onto the four top-level parameters. The parenthetical 'nothing is written to the skin' implicitly separates it from the editing tools, but no sibling such as set_points or get_preview is named explicitly, 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 Guidelines4/5

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

Gives real workflow guidance: this only changes preview state, and you should take a screenshot afterwards to observe the effect – routing the agent to the screenshot sibling. It stops short of stating when to prefer this over actually editing the skin (set_points/save) or reading state back (get_preview), so there are no explicit exclusions.

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