Skip to main content
Glama
rt-imaging-mcp

rt-imaging-mcp

by MLwithDyy

Read NIfTI header information

nifti_info
Read-onlyIdempotent

Extracts structural header details—shape, voxel size, data type, units, and orientation—from a NIfTI file without reading image data or free-text fields.

Instructions

Return shape, voxel size, data type, units and orientation of a NIfTI file.

Only structural header fields are returned. Free-text header fields and the image data are never read into the output.

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

Input Schema

NameRequiredDescriptionDefault
pathYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-redundant scope information: only structural header fields are emitted and free-text header fields plus image data are never read into output, which sets expectations about completeness of results. It stops short of stating error behavior for missing/unreadable files or supported extensions (.nii vs .nii.gz).

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 sentences, both front-loaded and content-bearing: the first states the output fields, the second delimits what is excluded. No filler, no repetition of the title or annotations.

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?

An output schema exists, so return values need no prose explanation, and the annotations fully cover the safety profile. The gap is the sole required parameter, whose accepted input form and error behavior are absent from both schema and description, leaving an agent to guess how to construct a valid call.

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 description coverage is 0% — the single 'path' parameter carries only a title, with no indication of whether it is a filesystem path, a URI, a file versus directory, or which extensions are accepted. The description does not compensate at all; the word 'path' never appears, so the only documented parameter is semantically 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?

The description opens with a concrete verb-and-resource pair and enumerates the exact fields returned (shape, voxel size, data type, units, orientation), which is far more specific than the tautological title. It never names a sibling, but the NIfTI-vs-DICOM resource split from the sibling tools is self-evident from the name and first sentence.

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?

Usage is only implied: an agent can infer this is the header-inspection tool for NIfTI files, and the second sentence usefully clarifies that it is not a full data reader. There is no explicit statement of when to prefer it, and no prerequisites or failure conditions for the path argument.

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