Skip to main content
Glama
Sign In
BonengDriveMCP

BonengDriveMCP

by time32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_parameter_set

Read-onlyIdempotent

Reads a stored offline parameter set by ID, clarifying that the returned values are not live device parameters.

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": {
      "set_id": "<set_id>"
    },
    "name": "get_parameter_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
set_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful context by flagging that the data is an offline snapshot rather than live device state. It says nothing about failure behavior for an unknown set_id or staleness of the stored set.

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?

One compact sentence, front-loaded with the action and followed by the important scope caveat. No wasted words, though the terseness comes at the cost of the missing parameter guidance.

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?

An output schema exists, so return values need not be described, and annotations cover safety. However, for a tool whose only input is an opaque ID, omitting any hint about sourcing set_id leaves a real gap for an agent choosing among many siblings.

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 description coverage is 0% and the single parameter set_id is undocumented in both the schema and the description. The description does not explain where set_id comes from (presumably list_parameter_sets) or its expected form, so it fails to compensate for the schema gap.

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+resource: reading one offline parameter set (读取一个离线参数集). It also immediately contrasts with live device parameters, which separates it from siblings like read_device_parameters or get_device_parameter_snapshot. It stops short of naming those siblings explicitly, so it isn't 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?

The clause '不代表设备实时参数' gives a clear when-this-is-not-the-right-tool condition and implicitly routes live reads to the device-read siblings. It does not name a concrete alternative tool or state prerequisites (e.g. that set_id should come from list_parameter_sets).

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