Skip to main content
Glama

load_data

Load spatial transcriptomics data into a SpatialDataset with cell/gene counts and metadata profiles. Supports Visium, Xenium, Slide-seq, MERFISH, seqFISH, and generic formats.

Instructions

Load spatial transcriptomics data with comprehensive metadata profile.

Args:
    data_path: Path to data file or directory
    data_type: 'visium', 'xenium', 'slide_seq', 'merfish', 'seqfish', or 'generic'
    name: Optional dataset name

Returns:
    SpatialDataset with cell/gene counts and metadata profiles

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
data_pathYes
data_typeYes
nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
nameYes
data_typeYes
descriptionNo
n_cellsNo
n_genesNo
spatial_coordinates_availableNo
tissue_image_availableNo
obs_columnsNo
var_columnsNo
obsm_keysNo
uns_keysNo
top_highly_variable_genesNo
top_expressed_genesNo
Behavior3/5

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

Annotations indicate readOnlyHint=false and openWorldHint=true, implying potential side effects and external access. The description adds the return type (SpatialDataset with cell/gene counts) but does not elaborate on side effects, permissions, data loading behavior, or error conditions. It provides adequate but not thorough transparency beyond annotations.

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?

The description is concise with a short opening sentence followed by a structured arg list. Every sentence provides useful information without redundancy. It is front-loaded with the main action and then details parameters efficiently.

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?

Given the tool's complexity (loading spatial data) and the presence of an output schema, the description covers the basic return type. However, it lacks details on file format requirements, error handling, performance considerations, or integration with other tools in the pipeline. It is minimally complete but leaves gaps.

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?

The input schema has 0% description coverage, so the description fully carries the burden. It explains each parameter clearly: data_path as file/directory, data_type with suggested enum values, and name as optional. This adds significant meaning beyond the schema's titles.

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 clearly states 'Load spatial transcriptomics data' with a verb and resource. It mentions 'comprehensive metadata profile' which adds specificity. However, it does not distinguish itself from the sibling tool 'reload_data', so it misses a chance to clarify when to use which.

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 does not provide guidance on when to use this tool versus alternatives like 'reload_data', 'preprocess_data', or 'analyze_*' tools. There is no mention of prerequisites, typical use cases, or limitations. The arg list gives parameter descriptions but no contextual usage advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cafferychen777/ChatSpatial'

If you have feedback or need assistance with the MCP directory API, please join our Discord server