Skip to main content
Glama
Augmented-Nature

ProteinAtlas MCP Server

search_cancer_markers

Find proteins linked to specific cancer types or with prognostic significance using Human Protein Atlas data.

Instructions

Find proteins associated with specific cancers or with prognostic value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cancerNoCancer type (e.g., breast cancer, lung cancer)
prognosticNoPrognostic filter
formatNoOutput format (default: json)
maxResultsNoMaximum number of results (1-10000, default: 100)

Implementation Reference

  • The handler function for 'search_cancer_markers' tool. Validates input using isValidPathologySearchArgs, constructs a search query based on cancer type and/or prognostic value, calls the shared searchProteins helper, and formats the response or error.
    private async handleSearchCancerMarkers(args: any) {
      if (!isValidPathologySearchArgs(args)) {
        throw new McpError(ErrorCode.InvalidParams, 'Invalid pathology search arguments');
      }
    
      try {
        let searchQuery = '';
        if (args.cancer) {
          searchQuery = `cancer:"${args.cancer}"`;
        }
        if (args.prognostic) {
          searchQuery += searchQuery ? ` AND prognostic:"${args.prognostic}"` : `prognostic:"${args.prognostic}"`;
        }
        if (!searchQuery) {
          searchQuery = 'prognostic:*'; // Search for any prognostic markers
        }
    
        const result = await this.searchProteins(searchQuery, args.format || 'json', undefined, 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 cancer markers: ${error instanceof Error ? error.message : 'Unknown error'}`,
            },
          ],
          isError: true,
        };
      }
    }
  • src/index.ts:574-587 (registration)
    Registration of the 'search_cancer_markers' tool in the tools list returned by ListToolsRequestSchema handler, including description and JSON input schema.
    {
      name: 'search_cancer_markers',
      description: 'Find proteins associated with specific cancers or with prognostic value',
      inputSchema: {
        type: 'object',
        properties: {
          cancer: { type: 'string', description: 'Cancer type (e.g., breast cancer, lung cancer)' },
          prognostic: { type: 'string', enum: ['favorable', 'unfavorable'], description: 'Prognostic filter' },
          format: { type: 'string', enum: ['json', 'tsv'], description: 'Output format (default: json)' },
          maxResults: { type: 'number', description: 'Maximum number of results (1-10000, default: 100)', minimum: 1, maximum: 10000 },
        },
        required: [],
      },
    },
  • Runtime type guard function used to validate input arguments for the search_cancer_markers handler, matching the inputSchema.
    const isValidPathologySearchArgs = (
      args: any
    ): args is { cancer?: string; prognostic?: string; format?: string; maxResults?: number } => {
      return (
        typeof args === 'object' &&
        args !== null &&
        (args.cancer === undefined || typeof args.cancer === 'string') &&
        (args.prognostic === undefined || ['favorable', 'unfavorable'].includes(args.prognostic)) &&
        (args.format === undefined || ['json', 'tsv'].includes(args.format)) &&
        (args.maxResults === undefined || (typeof args.maxResults === 'number' && args.maxResults > 0 && args.maxResults <= 10000))
      );
    };
  • src/index.ts:692-693 (registration)
    Switch case in CallToolRequestSchema handler that dispatches calls to 'search_cancer_markers' to the specific handler method.
    case 'search_cancer_markers':
      return this.handleSearchCancerMarkers(args);
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. It mentions the tool 'finds' proteins, implying a read operation, but lacks details on permissions, rate limits, data sources, or response format. This is inadequate for a search tool with multiple parameters and no output schema.

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 that front-loads the core functionality without any wasted words. It's 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 tool's moderate complexity (4 parameters, no annotations, no output schema), the description is incomplete. It lacks behavioral context, usage guidelines, and details on return values, which are crucial for effective tool invocation in this domain.

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 parameters. The description adds no additional meaning beyond implying that 'cancer' and 'prognostic' are key filters, but it doesn't explain parameter interactions or usage nuances, meeting the baseline for high schema 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 tool's purpose with a specific verb ('Find') and resource ('proteins'), specifying the context of cancer association and prognostic value. It distinguishes itself from siblings like 'search_proteins' by focusing on cancer markers, though it doesn't explicitly contrast with all siblings such as 'search_by_tissue' or 'search_by_subcellular_location'.

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. It doesn't mention sibling tools like 'search_proteins' or 'search_by_tissue', nor does it specify prerequisites, exclusions, or contextual cues for selection, leaving usage decisions ambiguous.

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