Skip to main content
Glama
Sign In
scpi-mcp

scpi-mcp

by armchairdeity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

measure

Take a single measurement on a specified analog channel, selecting from voltage, frequency, or time parameters like Vpp, Vrms, frequency, period, duty cycle, rise/fall time.

Instructions

Take a single measurement of one quantity on one channel.

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": {
      "channel": "<channel>",
      "kind": "<kind>"
    },
    "name": "measure"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesMeasurement to take. One of: 'vpp', 'vrms', 'vmax', 'vmin', 'frequency', 'period', 'duty', 'rise_time', 'fall_time'.
channelYesAnalog channel to measure, 1-based (1–4).

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"
-}
    • addedInput schema / properties / channel
      Added value: +{
+  "description": "Analog channel to measure, 1-based (1–4).",
+  "title": "Channel",
+  "type": "integer"
+}
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "Measurement to take. One of: 'vpp', 'vrms', 'vmax', 'vmin', 'frequency', 'period', 'duty', 'rise_time', 'fall_time'.",
+  "title": "Kind",
+  "type": "string"
+}
    • removedInput schema / properties / kwargs
      Removed value: -{
-  "title": "Kwargs"
-}
    • changedInput schema / required
      Previous value: -[
-  "args",
-  "kwargs"
-]New value: +[
+  "channel",
+  "kind"
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "measure_implDictOutput",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/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 of behavioral disclosure. It only describes the action without revealing side effects, permissions, or return behavior. For a read-like operation, minimal transparency is acceptable but not sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence with no wasted words. It is front-loaded with the core action. Could benefit from a slightly more structured format, but efficient overall.

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 low complexity (2 required params), full schema coverage, and the presence of an output schema, the description provides adequate information for a tool with such straightforward semantics.

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 coverage is 100%, so the input schema already documents both parameters (kind with allowed values, channel with range). The description adds no additional meaning beyond the schema, meriting a baseline score of 3.

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 clearly states the tool's action ('Take a single measurement') and resource ('one quantity on one channel'), effectively distinguishing it from siblings like measure_series which take multiple measurements.

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 usage for a single measurement on one channel, but does not explicitly state when to avoid this tool or mention alternatives. The context of sibling tools provides some contrast, but the description itself lacks explicit guidance.

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