Skip to main content
Glama
Sign In
DigitalMicrograph MCP

DigitalMicrograph MCP

by wuchqwq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

dm_open

Opens local DM data files such as dm3/dm4 and returns the image IDs in the document, loading acquisition metadata and calibrations with the file.

Instructions

在 DigitalMicrograph 中打开本地数据文件（dm3/dm4 及其它 DM 支持的格式），返回该文档内的图像 id 列表。dm3/dm4 的采集元数据与标定会随文件一起载入。

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>"
    },
    "name": "dm_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes绝对路径
showNo是否显示窗口，默认 true

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the tool returns a list of image ids and loads acquisition metadata/calibration for dm3/dm4 files, but it omits other relevant behavior: whether DigitalMicrograph must be running, what happens on invalid paths, and whether opening replaces or adds to existing documents.

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?

Two compact sentences with the main action and return value front-loaded. No sentence is redundant; the metadata-loading note adds useful context without bloat.

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 low-complexity file-opening tool without annotations or an output schema, the description covers the action, supported formats, return value, and metadata side effect. It is nearly complete but stops short of stating runtime prerequisites or error behavior.

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 description coverage is 100%, so the schema already explains both parameters fully. The description adds no parameter-level detail beyond what the schema provides, and the baseline score of 3 is appropriate.

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 ('open') and resource ('local data file') and lists supported formats plus the return value, so the core action is clear. It does not distinguish this tool from the sibling dm_4dstem_open, which is also a file-opening tool and may overlap with 'other DM-supported formats'.

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?

The description gives no guidance about when to use this tool versus alternatives such as dm_4dstem_open, nor any prerequisites or exclusions. Usage must be inferred entirely from the purpose statement.

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

Deploy Server

Other Tools