Skip to main content
Glama

annotate_cell_types

Annotate cell types in spatial transcriptomics data using reference methods like Tangram, scANVI, or marker-based approaches. Select method, reference dataset, and parameters to assign cell identities.

Instructions

Annotate cell types in spatial transcriptomics data.

Args:
    data_id: Dataset ID
    params: Annotation parameters (method, reference_data_id, cell_type_key, etc.)

Note: Reference methods (tangram, scanvi) require reference_data_id to be preprocessed first.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
data_idYes
paramsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
data_idYes
methodYes
output_keyYes
confidence_keyNo
cell_typesYes
countsYes
confidence_scoresNo
tangram_mapping_scoreNo
Behavior2/5

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

The description only mentions a prerequisite and does not disclose side effects (e.g., modifies data, returns annotation results) beyond what annotations imply.

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?

Extremely concise with three front-loaded sentences, each contributing essential information without waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite an output schema existing, the description is too brief for a complex tool with many parameters and method-specific behavior, lacking guidance on method selection and parameter relationships.

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?

Top-level parameters lack schema descriptions, so the brief summary of 'params' adds some value, but detailed semantics are left to the nested schema descriptions.

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?

Clearly states the action 'annotate' and target 'cell types in spatial transcriptomics data', distinguishing it from sibling analysis tools.

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?

Description notes a prerequisite for reference methods but does not explicitly state when to use this tool over alternatives or when not to use it.

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