Skip to main content
Glama
Augmented-Nature

ProteinAtlas MCP Server

get_tissue_expression

Retrieve tissue-specific protein expression data from the Human Protein Atlas to analyze where genes are active in the human body.

Instructions

Get tissue-specific expression data for a protein

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geneYesGene symbol
formatNoOutput format (default: json)

Implementation Reference

  • The main handler function that executes the 'get_tissue_expression' tool. Validates input using isValidGeneArgs, fetches tissue expression data via fetchTissueExpression, formats as JSON text response, and handles errors.
    private async handleGetTissueExpression(args: any) {
      if (!isValidGeneArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid gene arguments');
      }
    
      try {
        const result = await this.fetchTissueExpression(args.gene);
        return {
          content: [
            {
              type: 'text',
              text: JSON.stringify(result, null, 2),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching tissue expression: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Helper function that performs the actual API query for tissue expression data by calling searchProteins with specific tissue-related columns.
    private async fetchTissueExpression(gene: string): Promise<any> {
      const columns = ['g', 'eg', 'rnats', 'rnatd', 'rnatss', 't_RNA_adipose_tissue', 't_RNA_adrenal_gland', 't_RNA_brain', 't_RNA_breast', 't_RNA_colon', 't_RNA_heart_muscle', 't_RNA_kidney', 't_RNA_liver', 't_RNA_lung', 't_RNA_ovary', 't_RNA_pancreas', 't_RNA_prostate', 't_RNA_skeletal_muscle', 't_RNA_skin_1', 't_RNA_spleen', 't_RNA_stomach_1', 't_RNA_testis', 't_RNA_thyroid_gland'];
      return this.searchProteins(gene, 'json', columns, 1);
    }
  • src/index.ts:485-495 (registration)
    Tool registration entry in the tools array passed to server.setTools(), including name, description, and input schema.
      name: 'get_tissue_expression',
      description: 'Get tissue-specific expression data for a protein',
      inputSchema: {
        type: 'object',
        properties: {
          gene: { type: 'string', description: 'Gene symbol' },
          format: { type: 'string', enum: ['json', 'tsv'], description: 'Output format (default: json)' },
        },
        required: ['gene'],
      },
    },
  • src/index.ts:676-677 (registration)
    Switch case in the CallToolRequest handler that routes 'get_tissue_expression' calls to the handleGetTissueExpression method.
    case 'get_tissue_expression':
      return this.handleGetTissueExpression(args);
  • Input schema defining parameters for the tool: required 'gene' string and optional 'format' enum.
    inputSchema: {
      type: 'object',
      properties: {
        gene: { type: 'string', description: 'Gene symbol' },
        format: { type: 'string', enum: ['json', 'tsv'], description: 'Output format (default: json)' },
      },
      required: ['gene'],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the action without details on permissions, rate limits, data sources, or response behavior. It fails to address critical aspects like whether this is a read-only operation, potential data freshness, or error handling, leaving significant gaps.

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, direct sentence with no wasted words, effectively front-loading the core purpose. It is appropriately sized for the tool's complexity, making it easy to parse quickly.

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?

Given the lack of annotations and output schema, the description is insufficient for a tool that likely returns complex expression data. It does not explain return values, data structure, or potential limitations, leaving the agent under-informed about what to expect from the tool's behavior and outputs.

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 has 100% description coverage, documenting both parameters ('gene' and 'format') clearly. The description adds no additional meaning beyond the schema, such as examples or constraints, but the schema adequately covers the semantics, meeting the baseline for high coverage.

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 verb ('Get') and resource ('tissue-specific expression data for a protein'), making the purpose specific and understandable. However, it does not explicitly differentiate from siblings like 'get_blood_expression' or 'get_brain_expression', which might handle specialized subsets, leaving room for ambiguity in tool selection.

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?

No guidance is provided on when to use this tool versus alternatives such as 'search_by_tissue' or 'compare_expression_profiles'. The description lacks context about prerequisites, exclusions, or specific use cases, offering minimal assistance in tool selection among siblings.

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/Augmented-Nature/ProteinAtlas-MCP-Server'

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