Skip to main content
Glama
rt-imaging-mcp

rt-imaging-mcp

by MLwithDyy

Scan a directory for DICOM series

dicom_scan_directory
Read-onlyIdempotent

Inventory DICOM series under a directory, returning series IDs, modality, instance counts, and image size, with optional opaque paths to keep file and directory names hidden.

Instructions

Inventory DICOM series below a directory (path relative to the root).

Returns opaque series ids, modality, instance counts and image size. Study and series UIDs are never returned. Set opaque_paths=True to omit all file and directory names. Only DICOM Part 10 files (with the DICM preamble) are detected.

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

Input Schema

NameRequiredDescriptionDefault
directoryNo.
opaque_pathsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. Beyond that, the description adds genuinely load-bearing behavior: UIDs are never returned, opaque_paths=True strips all file and directory names, and only files with the DICM preamble are detected — three constraints an agent could not infer from the schema.

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 action, then progressively narrower constraints, with no filler sentences. The one sentence summarizing returned fields is mildly redundant given an output schema exists, but it is short and orients the agent.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter, read-only scanning tool with full annotation coverage and an output schema, this definition covers the gaps that matter: path semantics, detection criteria, and the privacy mode. Nothing needed to invoke it correctly is missing.

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?

Schema description coverage is 0%, so the description must carry the parameters, and it does for both: `directory` is defined as a path relative to the root, and `opaque_paths=True` is spelled out as omitting all file and directory names. Defaults ('.' and false) are left to the schema, which is acceptable.

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?

Opens with a specific verb+resource: "Inventory DICOM series below a directory." That is concrete enough for an agent to distinguish it from dicom_get_metadata, dicom_list_allowed_tags and nifti_info, though it never explicitly names those alternatives to reinforce the split.

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 gives operating context (the directory is relative to the root, only DICOM Part 10 files are detected) and states when to flip opaque_paths=True. It does not say when to prefer this scan over reaching for dicom_get_metadata, so the choice between siblings is only implied.

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