Skip to main content
Glama
Sign In
scpi-mcp

scpi-mcp

by armchairdeity
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

identify

Retrieves the vendor, model, serial number, and firmware version of the connected oscilloscope after configuration.

Instructions

Return the connected instrument's identity (vendor, model, serial, firmware).

Takes no arguments; requires a prior self_config.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • removedInput schema / properties / args
      Removed value: -{
-  "title": "Args"
-}
    • removedInput schema / properties / kwargs
      Removed value: -{
-  "title": "Kwargs"
-}
    • removedInput schema / required
      Removed value: -[
-  "args",
-  "kwargs"
-]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "identify_implDictOutput",
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description discloses that the tool takes no arguments and requires self_config. It does not mention side effects or error conditions, but for a simple identity retrieval this is minimally adequate.

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 extremely concise: two sentences, no fluff. The first sentence states purpose, the second adds constraints.

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 and presence of an output schema, the description adequately covers what it returns and the prerequisite. It could mention that it is a read-only operation, but not essential.

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

Parameters4/5

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

There are no parameters and schema coverage is 100%. The description adds value by explicitly stating 'Takes no arguments', which reinforces the empty schema.

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 returns the instrument's identity including vendor, model, serial, and firmware. It distinguishes from sibling tools which perform configuration or acquisition.

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 explicitly mentions that it requires a prior self_config, giving clear context for when to use it. However, it does not provide exclusions or alternatives for when not to use it.

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