Skip to main content
Glama
zinntikumugai

rigol-oscilloscope-mcp

by zinntikumugai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_afg_state

Retrieve current function generator settings, including output state and modulation, for a specific channel or all channels at once.

Instructions

Return the function generator settings, including whether the output is on.

With channel given, the settings of that channel are returned flat (channel, output, waveform, impedance, frequency_hz, amplitude_vpp, offset_v, phase_deg, duty_percent, symmetry_percent). With channel omitted, every generator channel is returned under channels, keyed by the channel number as a string: {"channels": {"1": {...}, "2": {...}}}.

output tells whether the generator is currently driving its connector. Reading never changes it. modulation reports the modulation settings (enabled, type, the effective type's depth/deviation, frequency_hz, waveform). This is read-only: it costs about 14 queries per channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/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 explicitly discloses that reading never changes output, that the operation is read-only, and that it costs about 14 queries per channel. It also explains the output and modulation semantics in useful detail.

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 detailed yet efficient. It front-loads the core purpose, then adds precisely the behavioral and structural details an agent needs. Every sentence contributes meaningful information without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema and no annotations, the description covers return shape, per-channel behavior, output semantics, modulation details, and performance cost. An agent can select and invoke this tool effectively with the information provided.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema provides no description for the channel parameter, but the description thoroughly explains both cases: with channel given returns flat settings, and with channel omitted returns all channels keyed by channel number as a string. This fully compensates for the 0% schema coverage.

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 and resource: 'Return the function generator settings, including whether the output is on.' This makes the tool's purpose immediately clear and distinct from sibling tools like configure_afg, enable_afg, and get_state.

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 description clearly implies this is for reading AFG state and explicitly notes it is read-only and 'never changes' the output. However, it does not explicitly name alternatives or state when not to use it, such as using configure_afg or enable_afg for changes.

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