Skip to main content
Glama
Augmented-Nature

ProteinAtlas MCP Server

get_protein_info

Retrieve detailed protein data including expression, localization, and pathology information from the Human Protein Atlas using gene symbols.

Instructions

Get detailed information for a specific protein by gene symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
geneYesGene symbol (e.g., BRCA1, TP53)
formatNoOutput format (default: json)

Implementation Reference

  • Main handler function for 'get_protein_info' tool that validates input, fetches protein data, and returns JSON response or error.
    private async handleGetProteinInfo(args: any) {
      if (!isValidGeneArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid gene arguments');
      }
    
      try {
        const result = await this.fetchProteinData(args.gene, args.format || 'json');
        return {
          content: [
            {
              type: 'text',
              text: typeof result === 'object' ? JSON.stringify(result, null, 2) : String(result),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error fetching protein info: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Input validation type guard 'isValidGeneArgs' used by the handler to check gene symbol and format parameters.
    const isValidGeneArgs = (
      args: any
    ): args is { gene: string; format?: string } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        typeof args.gene === 'string' &&
        args.gene.length > 0 &&
        (args.format === undefined || ['json', 'tsv', 'xml', 'trig'].includes(args.format))
      );
    };
  • src/index.ts:459-470 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and input schema definition.
    {
      name: 'get_protein_info',
      description: 'Get detailed information for a specific protein by gene symbol',
      inputSchema: {
        type: 'object',
        properties: {
          gene: { type: 'string', description: 'Gene symbol (e.g., BRCA1, TP53)' },
          format: { type: 'string', enum: ['json', 'tsv', 'xml', 'trig'], description: 'Output format (default: json)' },
        },
        required: ['gene'],
      },
    },
  • src/index.ts:671-672 (registration)
    Dispatch registration in CallToolRequestSchema switch statement routing to the handler.
    case 'get_protein_info':
      return this.handleGetProteinInfo(args);
  • Core helper method called by handler to fetch protein data via API search.
    private async fetchProteinData(gene: string, format: string = 'json'): Promise<any> {
      // Use searchProteins method which properly handles columns parameter
      return this.searchProteins(gene, format, undefined, 1);
    }
Behavior2/5

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

With no annotations, the description carries full burden but only states the basic action. It does not disclose behavioral traits such as rate limits, authentication needs, error handling, or what 'detailed information' includes (e.g., structure, function, interactions). This leaves significant gaps for a tool with potential complexity.

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, efficient sentence with zero waste. It is front-loaded with the core purpose and appropriately sized for a simple lookup tool.

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?

Given no annotations, no output schema, and 2 parameters with full schema coverage, the description is minimally adequate. It covers the basic purpose but lacks details on return values, error cases, or behavioral context, leaving room for improvement in completeness.

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 schema fully documents both parameters (gene symbol and format). The description adds no additional meaning beyond implying the gene parameter is required, which is already in the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 the resource 'detailed information for a specific protein', specifying the lookup method 'by gene symbol'. It distinguishes from siblings like 'get_protein_by_ensembl' (different identifier) and 'batch_protein_lookup' (batch vs single), but does not explicitly mention these distinctions.

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

Usage Guidelines3/5

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

The description implies usage when detailed protein information is needed for a single gene symbol, but provides no explicit guidance on when to choose this over alternatives like 'advanced_search' or 'batch_protein_lookup'. It lacks exclusions or prerequisites.

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