Skip to main content
Glama
taehojo
by taehojo

predict_splice_impact

Analyzes genetic variants to predict their impact on splicing, including splice sites and junctions, for investigating splicing alterations in genomic data.

Instructions

Focus on splicing-specific effects only.

Analyzes splice sites, splice site usage, and splice junctions.

Perfect for: investigating splicing variants, understanding splice alterations.

Example: "Analyze splicing impact of chr6:41129252C>T"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chromosomeYes
positionYes
refYes
altYes
tissue_typeNo

Implementation Reference

  • MCP CallTool request handler for 'predict_splice_impact': validates input using variantPredictionSchema, calls AlphaGenomeClient.predictSpliceImpact(), and returns JSON-formatted result as text content.
    case 'predict_splice_impact': {
      const params = validateInput(variantPredictionSchema, args) as VariantPredictionParams;
      const result = await getClient().predictSpliceImpact(params);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
  • Tool schema definition for 'predict_splice_impact' including name, description, and inputSchema with properties for chromosome, position, ref, alt, and optional tissue_type.
    export const PREDICT_SPLICE_IMPACT_TOOL: Tool = {
      name: 'predict_splice_impact',
      description: `Focus on splicing-specific effects only.
    
    Analyzes splice sites, splice site usage, and splice junctions.
    
    Perfect for: investigating splicing variants, understanding splice alterations.
    
    Example: "Analyze splicing impact of chr6:41129252C>T"`,
      inputSchema: {
        type: 'object',
        properties: {
          chromosome: { type: 'string', pattern: '^chr([1-9]|1[0-9]|2[0-2]|X|Y)$' },
          position: { type: 'number', minimum: 1 },
          ref: { type: 'string', pattern: '^[ATGCatgc]+$' },
          alt: { type: 'string', pattern: '^[ATGCatgc]+$' },
          tissue_type: { type: 'string' },
        },
        required: ['chromosome', 'position', 'ref', 'alt'],
      },
    };
  • src/index.ts:99-101 (registration)
    MCP ListTools request handler that returns ALL_TOOLS array containing PREDICT_SPLICE_IMPACT_TOOL.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: ALL_TOOLS };
    });
  • src/tools.ts:709-730 (registration)
    ALL_TOOLS array includes PREDICT_SPLICE_IMPACT_TOOL at position 6 (line 715), used for tool listing.
    export const ALL_TOOLS: Tool[] = [
      PREDICT_VARIANT_TOOL,
      BATCH_SCORE_TOOL,
      ASSESS_PATHOGENICITY_TOOL,
      PREDICT_TISSUE_SPECIFIC_TOOL,
      COMPARE_VARIANTS_TOOL,
      PREDICT_SPLICE_IMPACT_TOOL,
      PREDICT_EXPRESSION_IMPACT_TOOL,
      ANALYZE_GWAS_LOCUS_TOOL,
      COMPARE_ALLELES_TOOL,
      BATCH_TISSUE_COMPARISON_TOOL,
      PREDICT_TF_BINDING_IMPACT_TOOL,
      PREDICT_CHROMATIN_IMPACT_TOOL,
      COMPARE_PROTECTIVE_RISK_TOOL,
      BATCH_PATHOGENICITY_FILTER_TOOL,
      COMPARE_VARIANTS_SAME_GENE_TOOL,
      PREDICT_ALLELE_SPECIFIC_EFFECTS_TOOL,
      ANNOTATE_REGULATORY_CONTEXT_TOOL,
      BATCH_MODALITY_SCREEN_TOOL,
      GENERATE_VARIANT_REPORT_TOOL,
      EXPLAIN_VARIANT_IMPACT_TOOL,
    ];
  • AlphaGenomeClient method predictSpliceImpact that bridges to Python by calling callPythonBridge with action 'predict_splice_impact' and variant parameters.
    async predictSpliceImpact(params: VariantPredictionParams): Promise<any> {
      try {
        return await this.callPythonBridge('predict_splice_impact', {
          chromosome: params.chromosome,
          position: params.position,
          ref: params.ref,
          alt: params.alt,
          tissue_type: params.tissue_type,
        });
      } catch (error) {
        if (error instanceof ApiError) throw error;
        throw new ApiError(`Splice impact prediction failed: ${error}`, 500);
      }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'analyzes' and is for 'investigating,' which implies a read-only operation, but doesn't clarify if it's a prediction, simulation, or data retrieval tool. It lacks details on permissions, rate limits, output format, or any side effects. For a tool with 5 parameters and no annotation coverage, this is a significant gap in transparency.

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 appropriately sized and front-loaded, starting with the key constraint 'Focus on splicing-specific effects only.' Each sentence adds value: defining scope, listing analyses, providing usage context, and giving an example. There's no wasted text, though the structure could be slightly more polished for a perfect score.

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 (5 parameters, 0% schema coverage, no output schema, no annotations), the description is incomplete. It covers purpose and usage well but lacks parameter explanations, behavioral details, and output information. For a prediction/analysis tool in a server with many siblings, more context is needed to ensure the agent can use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate by explaining parameters. It doesn't mention any parameters explicitly, only implying through the example 'chr6:41129252C>T' which maps to chromosome, position, ref, and alt. It omits tissue_type entirely and provides no details on format, constraints, or meaning. With 5 parameters and low coverage, this is inadequate compensation.

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: 'Analyzes splice sites, splice site usage, and splice junctions' and provides a specific example. It distinguishes from siblings by focusing on 'splicing-specific effects only,' which helps differentiate it from tools like predict_expression_impact or predict_variant_effect. However, it doesn't explicitly name a resource or target beyond 'splicing variants,' making it slightly less specific than a perfect score.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: 'Focus on splicing-specific effects only' and 'Perfect for: investigating splicing variants, understanding splice alterations.' It implicitly distinguishes from siblings by narrowing to splicing, but it doesn't explicitly state when NOT to use it or name specific alternatives among the many sibling tools, which would be needed for a score of 5.

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/taehojo/alphagenome-mcp'

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