Skip to main content
Glama

advanced_read

Read-only

Execute a discovered read operation to inspect signals, retrieve screenshots, or fetch waveform data and images without changing acquisition or trigger settings.

Instructions

Execute a discovered read operation. Exact parameters come from discover_operations.

Screenshots return a saved artifact receipt; artifact.image explicitly retrieves the image. waveform.overview is a bounded saved-data envelope; waveform.image returns its optional PNG. Cannot change acquisition or channel/trigger settings.

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": {
      "operation": "<operation>"
    },
    "name": "advanced_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
argumentsNo
operationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with them. Beyond that it adds genuinely non-obvious behavior: screenshots yield an artifact receipt rather than inline data, and waveform.overview is a bounded envelope whose PNG is optional and retrieved separately. It still does not say what happens when the operation name is unknown or invalid.

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 core instruction is front-loaded in one sentence and the follow-up notes are short and scoped to specific cases. The telegraphic fragments ("Cannot change acquisition or channel/trigger settings.") read as notes rather than prose, which costs a little polish but not clarity.

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?

With no output schema, the description takes on the return-value burden and does address it for screenshots and waveform envelopes. For a generic dispatcher over an open-ended operation set, that is a reasonable level of coverage, though the return semantics of other operation families remain unstated.

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

Parameters2/5

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

Schema coverage is 0% for both parameters, so the description carries the full burden. It points to discover_operations as the source of the parameter contract, which is real direction, but it never explains the format of the required `operation` string or how the free-form `arguments` object is shaped or validated. The pointer is a partial compensation, not an adequate one.

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?

"Execute a discovered read operation" gives a specific verb and a scoped resource, and the discovery dependency is stated immediately. The agent can tell this is the generic read dispatcher rather than the control/mutation path, though the description never enumerates which operation families exist.

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?

It states the prerequisite plainly (parameters come from discover_operations) and routes two specific cases away from this tool toward artifact.image and waveform.image. It also excludes write usage (no acquisition/channel/trigger changes). What is missing is a comparison against the plain read siblings like waveform or measure, but names alone cannot establish their behavior, so no penalty is applied for that.

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