Skip to main content
Glama
Augmented-Nature

ProteinAtlas MCP Server

advanced_search

Search Human Protein Atlas data using multiple filters including tissue expression, subcellular location, cancer prognosis, protein class, and antibody reliability to find specific protein information.

Instructions

Perform advanced search with multiple filters and criteria

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoBase search query
tissueSpecificNoTissue-specific expression filter
subcellularLocationNoSubcellular localization filter
cancerPrognosticNoCancer prognostic filter
proteinClassNoProtein class filter
chromosomeNoChromosome filter
antibodyReliabilityNoAntibody reliability filter
formatNoOutput format (default: json)
columnsNoSpecific columns to include in results
maxResultsNoMaximum number of results (1-10000, default: 100)

Implementation Reference

  • The main handler function for the 'advanced_search' tool. Validates input, constructs a complex search query using multiple filters (tissue, location, prognostic, etc.), and delegates to the shared searchProteins method.
    private async handleAdvancedSearch(args: any) {
      if (!isValidAdvancedSearchArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid advanced search arguments');
      }
    
      try {
        let searchQuery = args.query || '';
    
        if (args.tissueSpecific) {
          searchQuery += (searchQuery ? ' AND ' : '') + `tissue:"${args.tissueSpecific}"`;
        }
        if (args.subcellularLocation) {
          searchQuery += (searchQuery ? ' AND ' : '') + `location:"${args.subcellularLocation}"`;
        }
        if (args.cancerPrognostic) {
          searchQuery += (searchQuery ? ' AND ' : '') + `prognostic:"${args.cancerPrognostic}"`;
        }
        if (args.proteinClass) {
          searchQuery += (searchQuery ? ' AND ' : '') + `class:"${args.proteinClass}"`;
        }
        if (args.chromosome) {
          searchQuery += (searchQuery ? ' AND ' : '') + `chromosome:"${args.chromosome}"`;
        }
        if (args.antibodyReliability) {
          searchQuery += (searchQuery ? ' AND ' : '') + `reliability:"${args.antibodyReliability}"`;
        }
    
        if (!searchQuery) {
          searchQuery = '*'; // Search for everything if no criteria specified
        }
    
        const result = await this.searchProteins(searchQuery, 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 in advanced search: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Type guard function for validating advanced_search input arguments.
    const isValidAdvancedSearchArgs = (
      args: any
    ): args is {
      query?: string;
      tissueSpecific?: string;
      subcellularLocation?: string;
      cancerPrognostic?: string;
      proteinClass?: string;
      chromosome?: string;
      antibodyReliability?: string;
      format?: string;
      columns?: string[];
      maxResults?: number;
    } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        (args.query === undefined || typeof args.query === 'string') &&
        (args.tissueSpecific === undefined || typeof args.tissueSpecific === 'string') &&
        (args.subcellularLocation === undefined || typeof args.subcellularLocation === 'string') &&
        (args.cancerPrognostic === undefined || typeof args.cancerPrognostic === 'string') &&
        (args.proteinClass === undefined || typeof args.proteinClass === 'string') &&
        (args.chromosome === undefined || typeof args.chromosome === 'string') &&
        (args.antibodyReliability === undefined || ['approved', 'enhanced', 'supported', 'uncertain'].includes(args.antibodyReliability)) &&
        (args.format === undefined || ['json', 'tsv'].includes(args.format)) &&
        (args.columns === undefined || Array.isArray(args.columns)) &&
        (args.maxResults === undefined || (typeof args.maxResults === 'number' && args.maxResults > 0 && args.maxResults <= 10000))
      );
    };
  • JSON Schema definition for the 'advanced_search' tool input, provided in the tool list response.
    inputSchema: {
      type: 'object',
      properties: {
        query: { type: 'string', description: 'Base search query' },
        tissueSpecific: { type: 'string', description: 'Tissue-specific expression filter' },
        subcellularLocation: { type: 'string', description: 'Subcellular localization filter' },
        cancerPrognostic: { type: 'string', description: 'Cancer prognostic filter' },
        proteinClass: { type: 'string', description: 'Protein class filter' },
        chromosome: { type: 'string', description: 'Chromosome filter' },
        antibodyReliability: { type: 'string', enum: ['approved', 'enhanced', 'supported', 'uncertain'], description: 'Antibody reliability filter' },
        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 },
      },
      required: [],
    },
  • src/index.ts:602-621 (registration)
    Registration of the 'advanced_search' tool in the list of available tools returned by ListToolsRequestSchema.
    {
      name: 'advanced_search',
      description: 'Perform advanced search with multiple filters and criteria',
      inputSchema: {
        type: 'object',
        properties: {
          query: { type: 'string', description: 'Base search query' },
          tissueSpecific: { type: 'string', description: 'Tissue-specific expression filter' },
          subcellularLocation: { type: 'string', description: 'Subcellular localization filter' },
          cancerPrognostic: { type: 'string', description: 'Cancer prognostic filter' },
          proteinClass: { type: 'string', description: 'Protein class filter' },
          chromosome: { type: 'string', description: 'Chromosome filter' },
          antibodyReliability: { type: 'string', enum: ['approved', 'enhanced', 'supported', 'uncertain'], description: 'Antibody reliability filter' },
          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 },
        },
        required: [],
      },
    },
  • src/index.ts:698-699 (registration)
    Dispatcher case in the CallToolRequestSchema handler that routes 'advanced_search' calls to the handler function.
    case 'advanced_search':
      return this.handleAdvancedSearch(args);
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 but offers minimal behavioral insight. It mentions 'advanced search' but doesn't disclose critical traits like whether it's read-only, potential rate limits, authentication needs, or what happens with large result sets. The description lacks details on output behavior, error handling, or performance characteristics, which are essential for a tool with 10 parameters.

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, efficient sentence that front-loads the core function ('Perform advanced search'). There's no wasted text, but it could be more structured by hinting at the domain or key filters. It's appropriately sized for a tool name like 'advanced_search,' though slightly more detail might improve clarity without sacrificing conciseness.

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 complexity (10 parameters, no annotations, no output schema), the description is inadequate. It doesn't explain what is being searched (e.g., proteins or biological data), the return format implications, or how filters interact. For a tool with many parameters and sibling alternatives, more context is needed to guide effective use, making it incomplete for an agent.

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 all 10 parameters with descriptions and constraints. The description adds no additional meaning beyond implying 'multiple filters,' which is redundant with the schema. With high coverage, the baseline is 3, as the description doesn't compensate but also doesn't detract from the well-documented schema.

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 the tool performs 'advanced search with multiple filters and criteria,' which indicates a search function but is vague about what domain or resource is being searched. It mentions 'multiple filters' but doesn't specify the target (e.g., proteins, genes, or data). This distinguishes it from simpler search siblings like 'search_by_tissue' but lacks specificity compared to others like 'search_cancer_markers.'

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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools like 'search_by_tissue' and 'search_cancer_markers,' it's unclear if this is a comprehensive search or when to prefer it over more specific tools. No exclusions, prerequisites, or context for usage are mentioned, leaving the agent to guess based on parameter names alone.

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