medimgq
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEDIMGQ_TS_ROOT | No | Location of the TotalSegmentator dataset. | ./Totalsegmentator_dataset_v201 |
| MEDIMGQ_BLOCKLIST | No | Path to the CSV file of cases a reviewer has rejected. | ./qc/blocklist.csv |
| MEDIMGQ_INDEX_DIR | No | Location where the indexes are stored. | ./data/index |
| MEDIMGQ_OUTPUT_DIR | No | Where images go when no output_dir is given. | ./outputs |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_structuresA | List labelable structures. |
| dataset_infoC | Filter values (pathology, study type, contrast phase), windows, presets, and option names. |
| list_findingsA | Pathology this dataset actually contains, found by measuring the segmentations (aneurysms, goiter, renal cysts, cardiomegaly, organ enlargement), with case counts. Also lists the coarse per-scan pathology categories from the dataset's metadata. |
| find_findingsB | Cases showing a measured finding (see list_findings), with the axial slice that best shows it.
|
| find_slicesC | Rank (case, view, slice) candidates where every structure is clearly visible.
|
| slice_contentsC | Structures visible on a slice (area, visibility), largest first. Use to choose distractors. |
| render_imageB | Render a specific slice with labels. Returns image path (+ base64), answer key with arrow/label
geometry, and optional hotspot masks (transparent PNGs, pixel-aligned with the image).
|
| labeled_imageC | Find a slice where every labeled structure (plus |
| batch_labeled_imagesA | Run many labeled_image requests into one folder with a manifest.jsonl (no base64 in the reply).
With |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a distinct primary role: metadata, structure listing, finding listing/search, slice search, slice contents, rendering, and batch rendering. The main overlap is that labeled_image is essentially a composite of find_slices + render_image, and batch_labeled_images is a batch variant, but the descriptions make their intended uses reasonably clear.
The names mix verb_noun patterns (list_structures, find_findings, render_image) with noun or adjective forms (dataset_info, slice_contents, labeled_image, batch_labeled_images). The convention is still readable, but it is not fully predictable across the set.
Nine tools fit the medical-imaging query/render workflow well, with each tool earning a place and no excessive surface area. The set is large enough to cover search, inspection, rendering, and batching without feeling bloated.
The surface covers metadata, structure/finding discovery, slice search, slice inspection, single rendering, and batch rendering, which are the core operations for this domain. Minor gaps exist, such as no explicit case-listing/get_case tool, but agents can work around them through find_* operations.