Skip to main content
Glama

set_timebase

Adjust the oscilloscope’s horizontal timebase in YT mode and read back the applied seconds-per-division, accounting for the instrument’s supported 1-2-5 rounding.

Instructions

Change horizontal scale in YT mode and read back the actual setting.

Requires --allow-control. Scope may round to a supported 1-2-5 scale.

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": {
      "seconds_per_division": "<seconds_per_division>"
    },
    "name": "set_timebase"
  }
}

Input Schema

NameRequiredDescriptionDefault
seconds_per_divisionYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare it is non-read-only, non-destructive and closed-world; the description adds real behavioral detail: a required control flag (authorization requirement) and the fact that the requested scope may round to a 1-2-5 scale, meaning the applied value can differ from the input. The readback clause further signals the response reflects the actual setting, which is useful beyond the annotations and output schema.

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 core action, with the prerequisite and rounding caveat appended. No filler or restatement of the title.

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?

With an output schema present and annotations covering safety, the description needs only to explain mutation behavior and constraints, which it does via the control flag and rounding note. It could go further by clarifying what 'YT mode' entails or what happens when --allow-control is absent.

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 0% for the single required parameter, so the description must carry the meaning. It implies the parameter is a horizontal scale value subject to 1-2-5 quantization, but never names the parameter, its unit (seconds per division), or a valid range.

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 gives a concrete verb and resource — 'Change horizontal scale in YT mode' — plus the readback behavior, so an agent knows this both mutates and returns the applied value. It does not explicitly contrast itself with sibling read/measure tools, keeping it below a 5.

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?

It states a hard prerequisite ('Requires --allow-control'), which is actionable context for when the call will succeed. However, it offers no guidance on when to prefer this over other timebase or measurement tools, nor any when-not-to-use condition.

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