Skip to main content
Glama
Sign In
mib2c-mcp

mib2c-mcp

by TomasSlekys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Zone file data

get_scene_data
Read-only

Retrieve zone-file scene data for the displayed car and side, including touch areas, part points, images, preview state, screen views, and undo status.

Instructions

The ambient light, climate or car status page's zone file for the shown car and side: touch areas (corners), feature / vent / part points with names, positions (and the saved ones when moved), their images and sizes, what the preview shows, screen views, undo state. Coordinates are picture pixels from the top-left; a point is its image's top-left corner.

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_scene_data"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations only declare readOnlyHint, while the description adds substantial behavioral context about the returned data model, including touch areas, points, saved positions, images and sizes, preview contents, screen views, and undo state. It also defines coordinate semantics (picture pixels from top-left, point anchored at its image's top-left), which is useful beyond what annotations provide.

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?

The content is front-loaded and every clause appears to add information, but it is delivered as one dense run-on sentence. A more structured list would make the return contents easier to parse.

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 no output schema and no parameters, the description carries the burden of explaining return content, and it enumerates the major data categories plus coordinate semantics. It still does not describe the output object structure or error behavior, so it is strong but not fully complete.

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?

There are zero input parameters, so the schema cannot document scoping. The description usefully clarifies that results are implicitly scoped to the 'shown car and side' rather than accepting car or side arguments.

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 the specific resource (the ambient light, climate, or car status page's zone file) and enumerates its contents for the shown car and side, making it distinguishable from generic state tools. It does not explicitly contrast with siblings such as get_state or get_preview, which keeps it from 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?

Provides no explicit when-to-use or when-not-to-use guidance relative to the many sibling getters. The only usage signal is the implied context of retrieving the zone file for the currently shown car and side.

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