Skip to main content
Glama

Explore singlecell

explore_singlecell
Read-onlyIdempotent

Inspect curated single-cell datasets, facets, expression summaries or a scoped expression query.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "explore_singlecell"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneNoRequired for search_gene and query_expression.
facetNoOptional facet name for dataset_facets, e.g. tissue, tissue_general, cell_type, disease, assay.
limitNoMaximum rows to return.
queryNoSearch terms for search_datasets.
actionNoOne of species, search_datasets, describe_dataset, dataset_facets, search_gene, query_expression.species
tissueNoOptional exact filter for query_expression.
speciesNoOne of human, mouse, marmoset, rhesus, chimpanzee.human
cell_typeNoOptional exact filter for query_expression.
min_cellsNoOptional minimum cell count for search_datasets.
dataset_idNoRequired for describe_dataset, dataset_facets, and query_expression.
min_pct_expNoOptional minimum percent expressing for query_expression.
tissue_generalNoOptional broad tissue filter for query_expression.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds only a high-level capability list and does not disclose meaningful behavioral traits beyond that, such as what 'scoped expression query' entails or how each action behaves.

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 a single front-loaded sentence with no wasted words. It is concise, though for a 12-parameter multi-action tool it could benefit from structure that maps capabilities to action modes.

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?

The tool is complex: 12 optional parameters, six action modes, and an output schema exists. The description does not orient the agent on how to select actions, what defaults matter, or when to prefer this tool over siblings. The schema mitigates this, but the description itself is incomplete for such a complex tool.

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 description coverage is 100%, so the input schema already fully documents all 12 parameters, including action-specific requirements. The description adds no additional parameter meaning, which is acceptable given the schema completeness but does not exceed the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a general verb ('Inspect') and lists several single-cell resource types, so the domain is clear. However, it does not clarify that the tool is action-dispatched across six distinct operations, nor does it distinguish itself from siblings like get_dataset or query_data. The purpose is understandable but vague for a multi-action tool.

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?

There is no explicit when-to-use guidance, no mention of alternatives, and no conditions for selecting among the six action modes. The description only lists capabilities in a single phrase, leaving the agent to infer usage from the schema alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources