Skip to main content
Glama

status

Read-only

Read acquisition state, timebase, channel scales, units, and probe ratios to inspect current oscilloscope setup before configuring captures.

Instructions

Read acquisition status, timebase, channel scales, units, and probe ratios.

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

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.7/5.0
Behavior3/5

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

The annotations already establish a read-only, closed-world operation, and the description's 'Read' wording is consistent with them. The field list adds useful scope, but the description does not clarify whether the values form a current snapshot or mention any acquisition-state considerations.

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?

A single front-loaded sentence pairs the operation with a precise, economical list of retrieved categories. There is no filler or redundant wording.

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?

For a zero-argument read with safety annotations and an output schema, the description is nearly sufficient for correct selection and invocation. Its main remaining gap is explicit guidance for choosing it over potentially related sibling operations.

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, so no argument syntax or semantics require explanation, giving the baseline score of 4. The description usefully defines the information retrieved without introducing any input requirements.

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 uses a specific verb and enumerates exactly what is read: acquisition status, timebase, channel scales, units, and probe ratios. Its scope is clear, but it does not explicitly distinguish the tool from any sibling.

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?

An agent can infer that the tool is appropriate when those status and configuration values are needed. However, there is no explicit when-to-use guidance, prerequisite, exclusion, or alternative-tool recommendation.

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