DigitalMicrograph MCP

Overview Schema Source Related Servers Discussions Admin

dm_4dstem_open

Opens and indexes a 4D-STEM dataset in uncompressed uint8 DM4 files by parsing only bounded headers, enabling chunked read-only access with explicit scan and detector axes.

Instructions

只读索引未压缩uint8 DM4中的唯一4D数据集。仅解析有界header，不整文件OpenImage；后续由Gatan原生只读binary stream按小块读取。显式NumPy轴scan_axes=[0,1]和detector_axes=[2,3]。

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": {
      "path": "<path>",
      "scan_axes": "<scan_axes>",
      "detector_axes": "<detector_axes>"
    },
    "name": "dm_4dstem_open"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes
`scan_axes`	Yes
`detector_axes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.0Oct 23, 2026

TDQS

B3.4/5.0

Behavior3/5

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

No annotations, so the description carries the burden. It does valuable disclosure: read-only, only parses a bounded header rather than fully opening the image, and later reads happen in small chunks via a native binary stream. But it omits failure behavior, permission/auth needs, and what a successful open returns.

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?

Front-loaded with the core purpose, then constraints, then axis semantics. Dense but every sentence carries information; no obvious waste.

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 and 3 fully required parameters at 0% schema coverage, the description should do more. It covers the axis parameters well but leaves path semantics and any notion of the returned handle or object unspecified.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate. It adds real meaning for scan_axes and detector_axes by giving the expected NumPy assignments ([0,1] and [2,3]), which the schema only describes as 2-element integer arrays. But the path parameter is left entirely undocumented.

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?

States a specific verb and resource: read-only indexing of the unique 4D dataset in uncompressed uint8 DM4 files. The purpose is clear, but it does not explicitly differentiate itself from siblings like dm_open or dm_4dstem_read, leaving the agent to infer the open-vs-read relationship.

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?

The description implies this is the first step before chunked reads (后续...按小块读取), giving implied usage, and it states a hard precondition (uncompressed uint8 only). However, it never explicitly says when to use this over dm_open or dm_4dstem_read.

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