Skip to main content
Glama
Augmented-Nature

ProteinAtlas MCP Server

search_proteins

Search the Human Protein Atlas database to find proteins using gene names, protein names, or descriptive keywords. Retrieve detailed expression and localization data in JSON or TSV format.

Instructions

Search Human Protein Atlas for proteins by name, gene symbol, or description

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query (gene name, protein name, or keyword)
formatNoOutput format (default: json)
columnsNoSpecific columns to include in results
maxResultsNoMaximum number of results (1-10000, default: 100)
compressNoWhether to compress the response (default: false)

Implementation Reference

  • MCP tool handler for 'search_proteins': validates input using isValidSearchArgs, calls the core searchProteins method, formats response as MCP content or error.
    private async handleSearchProteins(args: any) {
      if (!isValidSearchArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid search arguments');
      }
    
      try {
        const result = await this.searchProteins(args.query, args.format || 'json', args.columns, args.maxResults);
        return {
          content: [
            {
              type: 'text',
              text: typeof result === 'object' ? JSON.stringify(result, null, 2) : String(result),
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error searching proteins: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Core implementation: performs HTTP GET to Protein Atlas search API with query params, handles JSON/TSV formats, uses default columns for basic info.
    private async searchProteins(query: string, format: string = 'json', columns?: string[], maxResults?: number): Promise<any> {
      // Default columns if none provided - basic protein information
      const defaultColumns = ['g', 'gs', 'eg', 'gd', 'up', 'chr', 'pc', 'pe'];
      const searchColumns = columns && columns.length > 0 ? columns : defaultColumns;
    
      const params: any = {
        search: query,
        format: format,
        columns: searchColumns.join(','),
        compress: 'no',
      };
    
      const response = await this.apiClient.get('/api/search_download.php', { params });
    
      if (format === 'json') {
        return this.parseResponse(response.data, format);
      }
    
      return response.data;
    }
  • src/index.ts:444-458 (registration)
    Tool registration in ListToolsRequestHandler: defines name, description, and detailed inputSchema for MCP tool discovery.
    {
      name: 'search_proteins',
      description: 'Search Human Protein Atlas for proteins by name, gene symbol, or description',
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'Search query (gene name, protein name, or keyword)' },
          format: { type: 'string', enum: ['json', 'tsv'], description: 'Output format (default: json)' },
          columns: { type: 'array', items: { type: 'string' }, description: 'Specific columns to include in results' },
          maxResults: { type: 'number', description: 'Maximum number of results (1-10000, default: 100)', minimum: 1, maximum: 10000 },
          compress: { type: 'boolean', description: 'Whether to compress the response (default: false)' },
        },
        required: ['query'],
      },
    },
  • Type guard function for validating input arguments to search_proteins tool, matching the registered inputSchema.
    const isValidSearchArgs = (
      args: any
    ): args is {
      query: string;
      format?: string;
      columns?: string[];
      compress?: boolean;
      maxResults?: number;
    } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        typeof args.query === 'string' &&
        args.query.length > 0 &&
        (args.format === undefined || ['json', 'tsv', 'xml', 'trig'].includes(args.format)) &&
        (args.columns === undefined || Array.isArray(args.columns)) &&
        (args.compress === undefined || typeof args.compress === 'boolean') &&
        (args.maxResults === undefined || (typeof args.maxResults === 'number' && args.maxResults > 0 && args.maxResults <= 10000))
      );
    };
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the search functionality but lacks behavioral details: no mention of rate limits, authentication needs, pagination, error handling, or what the response contains (e.g., result structure). For a search tool with 5 parameters and no output schema, this is a significant gap.

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 front-loads the core purpose ('Search Human Protein Atlas for proteins') and specifies searchable fields concisely. Every word earns its place, 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 5 parameters, no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list of proteins with details), how results are ordered, or behavioral constraints. For a search tool in a rich sibling set, more context is needed to guide effective use.

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 parameters are well-documented in the schema. The description adds minimal value beyond the schema, only implying the 'query' parameter's purpose without detailing semantics for others like 'columns' or 'compress'. 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 action ('Search') and target resource ('Human Protein Atlas for proteins'), specifying searchable fields (name, gene symbol, description). It distinguishes from siblings like 'get_protein_by_ensembl' or 'search_by_tissue' by indicating broader keyword-based search, though not explicitly contrasting them.

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 explicit guidance on when to use this tool versus alternatives. Siblings include specialized tools like 'search_by_tissue' or 'get_protein_info', but the description doesn't mention these or provide context for choosing between them. Usage is implied by the search scope but not articulated.

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