Skip to main content
Glama

identify

Read-only

Reads the oscilloscope's model, serial number, firmware version, and simulator status so clients can verify the connected instrument before acquisition or decoding.

Instructions

Read model, serial, firmware, and whether this is a simulator.

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. First observedv0.6.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds one genuinely non-obvious behavioral detail — the simulator flag — which matters for interpreting later measurements. It says nothing about cost, latency, connection requirements, or whether it fails when no instrument is attached.

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?

A single front-loaded fragment with zero filler; every word names a returned datum. The elliptical phrasing (no explicit subject such as "device") is the only minor cost, though context makes it unambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a zero-argument read tool with an output schema, so return values need not be described in prose, and the annotations cover the safety profile. The description states what categories of information come back, which is exactly what an agent needs to decide to call it.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline is 4. The enumerated fields in the description are effectively return-value hints rather than parameter guidance.

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 supplies a specific verb ("Read") plus an enumerated payload: model, serial, firmware, and a simulator flag. That fully rescues the otherwise vague tool name "identify". It does not, however, distinguish the tool from siblings like "status" or "inspect_signal", which likely overlap in returning device information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as "status". The only steer is implicit: an agent infers this is the identity/bootstrap call from the listed fields. Nothing tells the agent when to prefer "identify" over "status".

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