Image Label MCP Server

Upload a whole slide

upload_slide

Upload whole-slide files (.svs, .ndpi, pyramidal TIFF, up to 5 GB) from the server host and start background analysis automatically.

Instructions

Upload a whole-slide file (.svs, .ndpi, pyramidal .tif/.tiff, up to 5 GB) from the machine running this server, and start its analysis in the background (see analyze_slide).

Input Schema

Name	Required	Description
`name`	No	Display name; defaults to the file name.
`path`	Yes	Absolute path of a whole-slide file (.svs, .ndpi or pyramidal .tif / .ome.tif, up to 5 GB) on the machine running this server.
`analyze`	No	Start a sample analysis (analyze_slide) as soon as the upload finishes.
`category`	No	Category to file the slide under (list_images filters by it).
`max_tiles`	No	Tiles to analyse for a sample (default 12 with cell types, 16 without).
`cell_types`	No	Also type each nucleus (tumour, immune, connective tissue, dead, normal epithelial); default on for a sample, off for full coverage.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.8.1Oct 28, 2026

addedInput schema / properties / analyze / description

Added value: +"Start a sample analysis (analyze_slide) as soon as the upload finishes."

addedInput schema / properties / category / description

Added value: +"Category to file the slide under (list_images filters by it)."

addedInput schema / properties / cell_types / description

Added value: +"Also type each nucleus (tumour, immune, connective tissue, dead, normal epithelial); default on for a sample, off for full coverage."

addedInput schema / properties / max_tiles / description

Added value: +"Tiles to analyse for a sample (default 12 with cell types, 16 without)."

addedInput schema / properties / name / description

Added value: +"Display name; defaults to the file name."

addedInput schema / properties / path / description

Added value: +"Absolute path of a whole-slide file (.svs, .ndpi or pyramidal .tif / .ome.tif, up to 5 GB) on the machine running this server."

Addedv0.8.0Oct 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations flag a non-read-only, non-idempotent write; the description adds real value by disclosing the background analysis kickoff and the size ceiling. It does not say what happens on a name collision or whether a re-upload duplicates or overwrites the slide.

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?

One sentence, format-and-limit constraint front-loaded, and the pointer to analyze_slide at the end. No wasted text.

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?

An output schema exists, so return values needn't be explained, and annotations carry the safety profile. The only meaningful gap is failure/overwrite behavior on an existing slide name.

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 100%, so formats, path semantics, analyze, max_tiles, cell_types and category are all already documented in the schema. The description adds no syntax or default detail beyond what the schema fields provide, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource (upload a whole-slide file), with accepted formats and the 5 GB cap stated inline. The phrase 'from the machine running this server' separates it from the sibling upload_slide_from_url without naming it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The local-file constraint plus the note that analysis starts in the background (see analyze_slide) gives clear usage context. It never explicitly says to prefer upload_slide_from_url for remote files, so an exclusion is implied rather than stated.

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