Skip to main content
Glama

get_summary

Retrieve a summary of an AnnData object from a .h5ad or .zarr file using its absolute path or URL.

Instructions

Get a summary of an AnnData object from a file or URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute path or URL to the AnnData file (.h5ad or .zarr)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoAny error message
n_obsNoThe number of observations (cells) in the AnnData object
X_typeNoThe type and dtype of the X attribute
layersNoThe layers of the AnnData object (always arrays), all with shape (n_obs, n_vars)
n_varsNoThe number of variables (genes) in the AnnData object
has_rawNoWhether the AnnData object has a raw attribute
uns_keysNoThe keys of the uns attribute and their types and shapes (if available, otherwise 'NA')
obsm_keysNoThe keys of the obsm attribute and their types and shapes
obsp_keysNoThe keys of the obsp attribute and their types, all with shape (n_obs, n_obs)
varm_keysNoThe keys of the varm attribute and their types and shapes
varp_keysNoThe keys of the varp attribute and their types, all with shape (n_vars, n_vars)
obs_columnsNoThe columns of the obs dataframe and their dtypes
var_columnsNoThe columns of the var dataframe and their dtypes
last_modifiedNoThe last modified time of the AnnData file in UTC, or None for URLs
Behavior2/5

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

With no annotations, the description carries the full burden. It states the input source but does not disclose whether the operation is read-only, what side effects might occur (e.g., network access), or what a 'summary' includes beyond the name.

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?

The description is a single clear sentence that immediately states the core function. No wasted words or structure issues.

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?

The tool is simple, has an output schema, and 100% parameter coverage. However, it lacks usage guidelines and behavioral transparency, leaving contextual gaps that prevent it from being fully complete for an agent deciding when to invoke it.

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%, with the description for 'path' already specifying absolute path or URL and file types (.h5ad/.zarr). The tool description adds no additional parameter context, so baseline 3 is appropriate.

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?

The description clearly states 'Get a summary of an AnnData object from a file or URL,' using a specific verb and resource. It distinguishes the purpose inherently from siblings by focusing on a high-level summary rather than raw data or descriptive statistics.

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

Usage Guidelines1/5

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

No guidance is provided about when to use this tool versus the sibling tools (view_raw_data, get_descriptive_stats). There are no context notes, alternatives, or exclusions.

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/biocontext-ai/anndata-mcp'

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