Skip to main content
Glama
Sign In
PPK2 MCP Server

PPK2 MCP Server

by andy-qingcai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_dut_power

Controls DUT power by switching output on or off in SOURCE mode, matching the official app's power button.

Instructions

DUT 电源开关(SOURCE 模式下接通/切断输出,等价官方 app 电源按钮)。

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": {
      "on": "<on>"
    },
    "name": "set_dut_power"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It conveys the effect (接通/切断输出) and app-equivalence, but says nothing about side effects on an in-progress measurement, whether the state persists, whether a mode precondition causes failure, or what errors/auth are involved for what is clearly a state-mutating operation.

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?

A single compact sentence with the core action front-loaded and the mode/app context in parentheses. Every clause earns its place; only the slightly terse parenthetical framing keeps it from being ideal.

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 one-parameter tool with no output schema, the essentials (what it toggles, in which mode) are present. But with zero annotations and no return/error description, an agent cannot predict failure conditions or side effects on ongoing captures, leaving meaningful gaps.

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 coverage is 0% and the single required boolean 'on' has no schema description. The description partially compensates by pairing 接通/切断 (connect/cut) with the output concept, implying on=true energizes the DUT, but it never explicitly binds true/false to those states.

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: toggling DUT power output, and clarifies it only makes sense in SOURCE mode and mirrors the official app's power button. This is far clearer than a bare name, though it does not explicitly distinguish itself from siblings like connect/disconnect or set_mode beyond the SOURCE-mode qualifier.

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 phrase 'SOURCE 模式下' implies the precondition that the device must already be in SOURCE mode, which is useful routing context. However, there is no explicit when-to-use guidance, no exclusion of alternatives (e.g., connect/disconnect), and no statement of what to do if the mode is wrong.

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