Skip to main content
Glama
Sign In
PXE200 SA MCP

PXE200 SA MCP

by apiwat59
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Sa Set

sa_set

Set any SAStudio4 value control (number, choice, or on-off) as a user would with read-back; mode-switching confirmation pop-ups are cancelled and reported.

Instructions

Set any SAStudio4 value control (number / choice / on-off) the way a user would, with read-back. Confirmation pop-ups that would switch mode are cancelled and reported.

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": {
      "name": "<name>",
      "value": "<value>"
    },
    "name": "sa_set"
  }
}

Input Schema

NameRequiredDescriptionDefault
menuNoMenu caption to disambiguate names used in several menus (e.g. 'channel')
modeNoMode the control belongs to (switches mode); blank = current
nameYesControl name from sa_controls
panelNoSide panel button: markerBtn | traceButton | graphTraceBtn
valueYesnumber WITH unit as on the keypad ('30kHz', '250ms', '-3dB', '2GB', '2001'), an option text for enums, On/Off for toggles
dialogNoDialog path, e.g. 'System/Preference', 'System/Amplitude Correction', 'Amplitude/AF'
confirmNoRequired for DANGER controls (RF output, input port, calibration tables...). Only after the user agreed.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses read-back behavior and that mode-switching confirmation pop-ups are cancelled and reported, but it does not cover permissions, destructive impact, persistence, or failure behavior beyond what the schema already implies.

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?

The description is two tight sentences, front-loaded with the main action and followed by a key behavioral nuance. Every sentence adds useful information with no wasted wording.

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?

Given the rich input schema, existing output schema, and 100% parameter description coverage, the description provides enough high-level context for an agent to understand the tool's role and key side effect. It falls short only in not explicitly routing between related sibling tools.

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 description coverage is 100%, so the detailed parameter descriptions already carry the semantic load. The description mentions that values are number / choice / on-off controls, but adds little beyond the schema's examples and documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Set') and resource ('any SAStudio4 value control'), with the target narrowed to number / choice / on-off controls. This implicitly distinguishes it from sibling tools that read (sa_get), press buttons (sa_press), or navigate dialogs (sa_dialog).

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 when to use the tool by scoping it to value controls and explaining that confirmation pop-ups that would switch mode are cancelled and reported. However, it never names alternatives such as sa_press, sa_dialog, or sa_configure, nor does it state when not to use this tool.

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