Skip to main content
Glama
Sign In

MBEstudio

by com.vectorstreamsystems
OverviewDiscussionsAdmin

Check drift

mbe_drift
Read-onlyIdempotent

Free. Compare a target's package with the model's current slice element by element: changed, only in the tool, or missing from it.

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": {
      "model_id": "<model_id>",
      "subsystem_id": "<subsystem_id>",
      "target": "<target>"
    },
    "name": "mbe_drift"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes
model_idYesA saved model id (m_ followed by 24 hex digits), as the studio and /v1/repos list them.
subsystem_idYesQualified name of a package or definition, e.g. "L4Robotaxi::NetworkSwitch".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the description does not need to repeat safety. It adds useful context beyond annotations by saying the operation is free and by describing the element-by-element comparison outcomes: changed, only in the tool, or missing.

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 description is compact and front-loads the cost cue before the main comparison behavior. It is appropriately sized, though phrases like 'missing from it' and 'only in the tool' are slightly ambiguous about the exact comparison direction.

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 three-parameter read-only comparison tool with no output schema, the description covers the core operation and result categories. However, it omits routing guidance relative to mbe_diff and leaves the target parameter's meaning only partially defined.

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 67%: model_id and subsystem_id are documented, but target has no schema description. The description helps conceptually by framing target as 'a target's package' and model_id as 'the model's current slice', but it does not explain target format or fully compensate for the missing parameter documentation.

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, 'Compare', and two resources: a target's package and the model's current slice. It clearly conveys a drift-checking purpose, but it does not name or distinguish itself from the sibling tool mbe_diff, leaving some ambiguity.

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?

The only usage-oriented cue is 'Free.', which hints at cost but does not explain when to choose this tool over alternatives. There is no explicit when-to-use, when-not-to-use, or comparison with mbe_diff, so the agent must infer usage from the purpose alone.

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

All MBEstudio toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources