Skip to main content
Glama
Sign In
JDS2800 MCP

JDS2800 MCP

by ikatkov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_mode

Destructive

Stops current actions, selects and verifies a JDS2800 signal generator operating mode such as wave, measure, counter, sweep, pulse, burst, or system.

Instructions

Stop current actions, select the operating mode and verify 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": {
      "mode": "<mode>"
    },
    "name": "set_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already mark it as destructive and non-idempotent. The description adds two useful behavioral details beyond annotations: it stops current actions (clarifying what is disrupted) and it verifies the selected mode (post-condition check). It still omits any permission or blocking behavior details.

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?

A single sentence, front-loaded with the destructive side effect and then the selection and verification steps. Every word earns its place; no filler.

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-param enum tool with safety annotations and no output schema, the description covers the basic action and side effect. It omits what the modes mean and how the tool relates to siblings like configure_channel, leaving the agent with an incomplete operational picture.

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 'mode' parameter is an enum with nine values, none explained. The description says 'operating mode' but does not add meaning for any enum value or constraints, 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?

The description names a specific action ('select the operating mode') and a concrete side effect ('Stop current actions'), so the purpose is clear. However, it offers no differentiation from siblings such as configure_channel or set_outputs, which could also change device behavior.

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?

Usage is implied: use this tool to change the operating mode, and be aware it stops current actions. There is no explicit guidance on when to choose set_mode over configure_channel/set_outputs or when not to use it.

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