Skip to main content
Glama
Sign In
BonengDriveMCP

BonengDriveMCP

by time32
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_network_selection

Read-onlyIdempotent

View the saved network device selection to confirm which device is configured; note that selection status does not mean the device is online.

Instructions

查看当前保存的网络设备选择；选择状态不表示设备在线。

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds a genuinely useful behavioral caveat — that a saved selection does not mean the device is online — which prevents an agent from treating the result as connectivity confirmation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact clauses separated by a semicolon, with the action stated first and the crucial caveat second. Every phrase adds information and nothing is padded.

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?

An output schema exists, so return-value details are unnecessary, and annotations cover the safety profile. The only remaining gap is that the caveat about offline devices does not route the agent to a specific tool (e.g., a selected-device probe) — a minor omission for a simple getter.

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?

A parameter-free tool with 100% schema coverage, so no parameter explanation is needed and the schema covers what would otherwise be a gap. The baseline score for zero parameters applies, with nothing lost and nothing to compensate for.

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 Chinese text names a specific verb-and-resource pair: '查看' (view) retrieves '当前保存的网络设备选择' (the currently saved network device selection). An agent can immediately tell this is a read of persisted selection state as opposed to the pairing sibling 'select_network_device', though the description never names that sibling explicitly.

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?

The description implies usage by pairing 'view' with 'currently saved', which suggests reading the stored selection at the start of a workflow. But it gives no explicit when-to-use guidance, no exclusions, and does not point at the alternative tools (such as probing the selected device) for verifying that selection.

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