ProteinAtlas MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_proteinsC | Search Human Protein Atlas for proteins by name, gene symbol, or description |
| get_protein_infoB | Get detailed information for a specific protein by gene symbol |
| get_protein_by_ensemblC | Get protein information using Ensembl gene ID |
| get_tissue_expressionC | Get tissue-specific expression data for a protein |
| search_by_tissueC | Find proteins highly expressed in specific tissues |
| get_blood_expressionC | Get blood cell expression data for a protein |
| get_brain_expressionC | Get brain region expression data for a protein |
| get_subcellular_locationC | Get subcellular localization data for a protein |
| search_by_subcellular_locationC | Find proteins localized to specific subcellular compartments |
| get_pathology_dataB | Get cancer and pathology data for a protein |
| search_cancer_markersC | Find proteins associated with specific cancers or with prognostic value |
| get_antibody_infoB | Get antibody validation and staining information for a protein |
| advanced_searchC | Perform advanced search with multiple filters and criteria |
| batch_protein_lookupC | Look up multiple proteins simultaneously |
| compare_expression_profilesC | Compare expression profiles between multiple proteins |
| get_protein_classesC | Get protein classification and functional annotation data |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Every tool has a clearly distinct purpose with no ambiguity. For example, 'get_protein_info' retrieves general details, while 'get_subcellular_location' focuses on localization, and 'search_by_tissue' finds proteins based on tissue expression. The descriptions clearly differentiate between retrieval, search, and comparison operations.
Tool names follow a highly consistent verb_noun pattern throughout, such as 'get_protein_info', 'search_proteins', and 'compare_expression_profiles'. All tools use snake_case with clear, descriptive verbs like 'get', 'search', and 'compare', making the naming predictable and easy to understand.
With 16 tools, the count is well-scoped for a comprehensive protein atlas server. Each tool earns its place by covering distinct aspects like expression data, pathology, searches, and comparisons, without feeling excessive or thin for the domain's complexity.
The tool surface provides complete coverage for the protein atlas domain, including retrieval (e.g., 'get_protein_info'), search (e.g., 'search_proteins'), comparison (e.g., 'compare_expression_profiles'), and specialized data access (e.g., 'get_pathology_data'). There are no obvious gaps, supporting full agent workflows from basic lookups to advanced analyses.