Skip to main content
Glama
Sign In
BonengDriveMCP

BonengDriveMCP

by time32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

plan_batch_configuration

Read-onlyIdempotent

Preview batch configuration changes and pending validation items before applying them; note that deleting a parameter keeps the device's original value and execution is not currently supported.

Instructions

预览批量修改及待验证项；文件中删除参数表示保留设备原值，当前不能执行。

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": {
      "baseline_id": "<baseline_id>",
      "target_id": "<target_id>"
    },
    "name": "plan_batch_configuration"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
target_idYes
baseline_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds two non-obvious points: deleting a parameter in the file means retaining the device's original value, and execution is currently unavailable. These are useful beyond the annotations, though pagination and validation-item behavior are not described.

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?

It is a single compact statement with the preview purpose front-loaded, followed by the two key caveats. It is dense but contains no obvious filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has four parameters, no schema descriptions, and an output schema; the description covers purpose and a no-execution caveat but leaves the required baseline/target semantics and pagination unexplained. For a planning tool whose inputs determine the comparison, this is a material completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, yet the description does not explain baseline_id, target_id, limit, or offset. It refers to a 'file' whose deleted parameters are treated as keep-original, but no file parameter appears in the schema, which adds ambiguity rather than clarifying the four inputs.

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 action—preview batch modifications and pending validation items—so the agent knows this is a planning/preview tool rather than an executor. It does not explicitly name how it differs from sibling prepare/apply tools, but the verb and resource are clear.

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?

It states 'currently cannot execute', which tells the agent this is preview-only and prevents misuse as an apply tool. However, it does not name the alternative execution tool or specify when to choose this over prepare_device_parameter_write or apply_device_parameter_write.

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