Skip to main content
Glama
Sign In
scpi-mcp

scpi-mcp

by armchairdeity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_timebase

Adjust the horizontal scale and trigger offset to control the number of signal periods displayed.

Instructions

Set the horizontal time base (seconds/div and trigger offset).

Controls how many periods of the signal are shown; widen s/div to see slow events, narrow it to resolve fast ones. Shared across all channels.

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
scaleNoHorizontal scale in seconds per division (e.g. 1e-3 = 1 ms/div). None leaves it unchanged.
offsetNoHorizontal (trigger) offset in seconds, moving the trigger point left/right. None leaves it unchanged.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • removedInput schema / properties / args
      Removed value: -{
-  "title": "Args"
-}
    • removedInput schema / properties / kwargs
      Removed value: -{
-  "title": "Kwargs"
-}
    • addedInput schema / properties / offset
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Horizontal (trigger) offset in seconds, moving the trigger point left/right. None leaves it unchanged.",
+  "title": "Offset"
+}
    • addedInput schema / properties / scale
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Horizontal scale in seconds per division (e.g. 1e-3 = 1 ms/div). None leaves it unchanged.",
+  "title": "Scale"
+}
    • removedInput schema / required
      Removed value: -[
-  "args",
-  "kwargs"
-]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "set_timebase_implDictOutput",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries full behavioral burden. It discloses that changes are shared across channels but omits potential side effects, destructiveness, or prerequisites. More context on what happens when called (e.g., does it reset other settings?) would improve transparency.

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 sentences with front-loaded purpose. Each sentence adds value: first defines the operation, second provides usage context and scope. No wasted words.

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 tool's simplicity (2 optional params) and presence of an output schema, the description covers key aspects: purpose, usage guidelines, and scope. It could mention typical return value or error states but is mostly complete.

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%, with each parameter already explained with units and default behavior. The tool description adds minimal extra meaning (e.g., 'trigger offset' phrasing already in schema), so baseline 3 is appropriate.

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 clearly states it sets horizontal time base (seconds/div and trigger offset) and explains the effect on signal display. It implicitly distinguishes from sibling tools like set_channel and set_trigger by focusing on timebase, but does not explicitly differentiate.

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 provides practical guidance: widen s/div for slow events, narrow for fast ones. It also notes the setting is shared across all channels. However, it lacks explicit when-not-to-use or alternatives.

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