Skip to main content
Glama

load_data

Load spatial transcriptomics data (Visium, Xenium, etc.) along with comprehensive metadata for analysis. Returns a SpatialDataset object with cell and gene counts.

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
nameNo
data_pathYes
data_typeYes

Output Schema

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

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

Annotations indicate readOnlyHint=false (modifies state) and idempotentHint=false (not idempotent). The description adds 'Load' which is a write operation, consistent with annotations, but does not detail side effects like overwriting or validation.

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 clear docstring structure (Args, Returns). It includes essential info without fluff, though it could be more front-loaded by putting the purpose first rather than after the blank line.

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 complexity of spatial transcriptomics and the existence of an output schema, the description covers basic usage and return type. However, it lacks guidance on error conditions, performance, or behavior for overlapping data, which would make it more complete.

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?

Despite 0% schema description coverage, the description explains each parameter's purpose (path, type list, optional name) in the docstring, adding meaning beyond the schema's bare titles. More detail on file formats would improve it.

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 it loads spatial transcriptomics data with a comprehensive metadata profile, using a specific verb and resource. It distinguishes from sibling tools like 'reload_data' by focusing on initial loading, though it doesn't explicitly differentiate.

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 implies use when loading data, but does not provide explicit guidance on when to use this tool vs. alternatives like 'reload_data' or other specialized loaders. No exclusions or context are given.

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