Skip to main content
Glama

get_region_info

Retrieve genomic region data from gnomAD v4, including variant information and population frequencies for specified chromosome coordinates in GRCh38.

Instructions

[gnomAD API] Retrieve region information (v4 only) Args: reference_genome (str): Reference genome (GRCh38) chrom (str): Chromosome start (int): Start position. Build must be GRCh38. stop (int): End position. Build must be GRCh38. Returns: dict: region info Note: Not supported in v2/v3.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reference_genomeYes
chromYes
startYes
stopYes
datasetNognomad_r4

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.py:64-97 (handler)
    The get_region_info tool is defined and implemented as an MCP tool in server.py. It takes region parameters, validates them, and calls run_query_with_metadata to fetch data.
    @mcp.tool()
    def get_region_info(
        reference_genome: str,
        chrom: str,
        start: int,
        stop: int,
        dataset: str = 'gnomad_r4'
    ) -> dict:
        """
        [gnomAD API] Retrieve region information (v4 only)
        Args:
            reference_genome (str): Reference genome (GRCh38)
            chrom (str): Chromosome
            start (int): Start position. Build must be GRCh38.
            stop (int): End position. Build must be GRCh38. 
        Returns:
            dict: region info
        Note:
            Not supported in v2/v3.
        """
    
        if dataset != 'gnomad_r4':
            raise ValueError("Only v4 is supported for region info.")
        if reference_genome != 'GRCh38':
            raise ValueError("Only GRCh38 is supported for region info.")
    
        variables = {
            'dataset': dataset,
            'reference_genome': reference_genome,
            'chrom': chrom,
            'start': start,
            'stop': stop,
        }
        return run_query_with_metadata('region', variables)
Behavior2/5

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

With no annotations provided, the description carries full burden but provides minimal behavioral context. It mentions API version constraints ('v4 only') and build requirements ('GRCh38'), but doesn't disclose authentication needs, rate limits, error conditions, or what 'region info' contains beyond the return type. For a tool with 5 parameters and no annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is reasonably concise but has structural issues. The Args/Returns/Note sections are clear, but the opening line could be more front-loaded. The 'Note' about version support is important but could be integrated more smoothly. Some redundancy exists ('GRCh38' mentioned twice in parameter descriptions).

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 5 parameters with 0% schema coverage, no annotations, but with an output schema (which handles return values), the description is moderately complete. It covers most parameters and provides version constraints, but lacks behavioral context like authentication, rate limits, or error handling that would be important for API tool usage.

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 but only partially does. It explains 4 parameters (reference_genome, chrom, start, stop) with some constraints ('Build must be GRCh38'), but doesn't mention the 5th parameter 'dataset' with its default value 'gnomad_r4'. The description adds meaning for 4/5 parameters but leaves one completely undocumented.

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 ('Retrieve region information') and specifies the resource ('gnomAD API'), but doesn't explicitly differentiate from sibling tools like 'get_gene_info' or 'get_variant_info' which likely retrieve different types of genomic data. The 'v4 only' qualification adds specificity but not sibling differentiation.

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 provides implicit guidance through the 'v4 only' note and parameter constraints ('Build must be GRCh38'), suggesting when this tool is applicable. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_gene_info' for gene-level data or 'search_for_variants' for variant searches.

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/koido/gnomad-mcp'

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