Skip to main content
Glama
nk-dho924s-mcp

nk-dho924s-mcp

by bigtimer-dev

screenshot

Captures the oscilloscope's current display as a 1024x600 PNG image for documentation, sharing, or analysis.

Instructions

Capture the scope screen as a PNG image (1024x600).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 supplied, so the description carries the full burden, and it says nothing about side effects, whether the instrument state changes, latency, or how the image is delivered. It only discloses the format and pixel dimensions, which is minimal behavioral context for an unannotated tool.

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 with zero filler; the format and resolution are appended where they add the most value.

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

Completeness3/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 usefully states the return artifact is a PNG at 1024x600, which partially compensates. However, it does not say how the image is returned (inline payload, base64, or file path) or whether a follow-up call is needed to retrieve it, leaving a real gap for an agent wiring up the call.

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 the baseline is 4 and there is nothing further the description could clarify about inputs. No meaningful gap exists on this dimension.

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 names a specific verb ('Capture'), a specific resource ('the scope screen'), and the output artifact type with dimensions ('PNG image (1024x600)'). This makes it unmistakable against siblings like get_waveform, measure, or scpi, which deal with data and commands rather than a rendered display.

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 guidance on when to use this versus the eight siblings, no mention of prerequisites (e.g., display must be on), and no exclusions. An agent must infer that it is for visual snapshots rather than data extraction.

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