Skip to main content
Glama
nk-dho924s-mcp

nk-dho924s-mcp

by bigtimer-dev

set_timebase

Configure the oscilloscope's horizontal scale (s/div) and trigger position offset (s), returning the updated timebase.

Instructions

Set horizontal scale (s/div) and/or trigger position offset (s). Returns the new timebase.

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": "set_timebase"
  }
}

Input Schema

NameRequiredDescriptionDefault
offset_sNo
scale_s_divNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a mutation tool. It discloses only that it returns the new timebase; it says nothing about validation ranges, error behavior for out-of-range scales, whether the change persists across acquisitions, or how trigger offset interacts with set_trigger. That is a thin disclosure for an unannotated write operation.

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 short sentences, front-loaded with the mutation and followed by the return value, with no filler. Nothing could be removed without losing information.

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?

Output schema exists, so the return-value sentence is supplementary rather than required, and the tool is a simple two-parameter setter. The remaining gap is operational context: valid ranges and whether an omitted parameter leaves that setting untouched.

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%, so the description must carry parameter meaning, and it only partially does. It gives units (s/div and s) that the property names already hint at, but never explains that null/omitted leaves that axis unchanged, nor gives acceptable ranges or any interaction between the two parameters.

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 and resource ('Set horizontal scale... and/or trigger position offset') with units for both, so an agent knows exactly which instrument property changes. It is distinguishable from set_channel and set_trigger by the 'horizontal scale/timebase' scope, though it never names those siblings to reinforce the boundary.

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 'and/or' phrasing implies both parameters are optional and either can be supplied alone, which is usable context. However, there is no guidance on when to prefer this over set_trigger for the trigger-position part, and no prerequisites such as whether acquisition must be running or stopped.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.