Skip to main content
Glama

view_raw_data

Access raw data from AnnData objects by selecting an attribute (X, obs, var, etc.) and applying slicing or filters to inspect specific rows, columns, or gene subsets.

Instructions

View the raw data of an AnnData object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoThe key of the attribute value to view. Can be a single string or a list of strings for nested key retrieval (e.g., ['key1', 'key2'] to access attr_obj['key1']['key2']).
pathYesAbsolute path or URL to the AnnData file
attributeYesThe attribute to view
filter_valueNoThe value(s) to filter the dataframe by.
filter_columnNoThe column name of the dataframe to filter by. Only applicable when the selected attribute (or attribute value) is a dataframe. Must be provided TOGETHER with filter_operator and filter_value.
col_stop_indexNoThe stop index for the column slice. Only applied to attributes or attribute values with a suitable type.
row_stop_indexNoThe stop index for the row slice. Only applied to attributes or attribute values with a suitable type.
col_start_indexNoThe start index for the column slice. Only applied to attributes or attribute values with a suitable type.
filter_operatorNoThe operator to use for the dataframe filter.
row_start_indexNoThe start index for the row slice. Only applied to attributes or attribute values with a suitable type.
columns_or_genesNoColumn names or gene names to select. For pandas.DataFrame attributes (e.g., obs, var), these are column names. For 'X' or 'layers' attributes, these are gene names (from var_names) and are used instead of col_start_index/col_stop_index. If None, the entire attribute is considered or col_start_index/col_stop_index is used. Also accepts glob-like patterns as input, e.g. ['RE*', 'CD4*'].

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoThe data to view, e.g. a slice of a pandas.DataFrame or a numpy array in csv format. Other data types are converted to a plain string.
errorNoAny error message
data_typeNoThe original type of the data
full_shapeNoThe full shape of the data, before slicing, if applicable, otherwise 'NA'
slice_shapeNoThe shape of the data after slicing, if applicable, otherwise 'NA'
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The phrase 'View the raw data' implies a read-only operation, but it does not explicitly state side effects, data safety, authentication needs, or how output is structured. There is no information about slicing limits or potential performance implications, which is a significant gap for an 11-parameter tool.

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 extremely concise (one sentence) and directly states the core purpose without redundancy. It is front-loaded and efficient, though it may be too terse given the tool's complexity, but conciseness itself is well-served.

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 having a rich schema and output schema, the description does not explain the tool's behavior such as how raw data is formatted, the effect of row/column slicing, or interaction with filter parameters. For a tool with 11 parameters and complex semantics (e.g., nested key access, glob patterns), this single sentence is insufficient to convey the full capability, leaving the agent to discover behavior through the schema alone.

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?

The input schema provides descriptions for all 11 parameters (100% coverage), including nested key retrieval, filter operators, and column/gene selection. Since the schema fully documents parameter meanings, the description does not need to add extra details, and a baseline score of 3 is appropriate.

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 the action ('View') and resource ('raw data of an AnnData object'), which is distinct from the sibling tools get_summary and get_descriptive_stats that imply aggregated views. However, it does not explicitly differentiate itself, relying on the tool name and minimal description.

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 provides no guidance on when to use this tool versus the siblings, nor any prerequisites or context such as when raw data viewing is appropriate. It is a single sentence with no alternatives or exclusions mentioned, leaving the agent to infer usage.

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