Skip to main content
Glama

search_for_genes

Search for genes in the Genome Aggregation Database (gnomAD) to retrieve gene metadata across versions v2, v3, and v4 using specified datasets and reference genomes.

Instructions

[gnomAD API] Search for genes (v2/v3/v4) Args: dataset (str): gnomAD dataset ID (gnomad_r3/gnomad_r2_1) reference_genome (str, optional): Reference genome (GRCh37 or GRCh38) query (str): Search string Returns: dict: search results

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetYes
reference_genomeYes
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • server.py:41-61 (handler)
    The implementation of the search_for_genes tool handler.
    @mcp.tool()
    def search_for_genes(
        dataset: str,
        reference_genome: str,
        query: str
    ) -> dict:
        """
        [gnomAD API] Search for genes (v2/v3/v4)
        Args:
            dataset (str): gnomAD dataset ID (gnomad_r3/gnomad_r2_1)
            reference_genome (str, optional): Reference genome (GRCh37 or GRCh38)
            query (str): Search string
        Returns:
            dict: search results
        """
        variables = {
            'dataset': dataset,
            'reference_genome': reference_genome,
            'query': query
        }
        return run_query_with_metadata('gene_search', variables)
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 mentions the API and dataset versions (v2/v3/v4) but lacks critical behavioral details such as authentication needs, rate limits, error handling, or what 'search results' entail beyond a dict return.

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 structured with sections for Args and Returns, but includes redundant information (e.g., repeating parameter names without added value). It's moderately concise but could be more front-loaded with essential usage context.

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?

An output schema exists, so return values needn't be explained. However, with 3 parameters at 0% schema coverage and no annotations, the description provides only basic parameter hints and lacks completeness for effective tool use, such as examples or constraints.

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. It lists parameters with brief notes (e.g., 'gnomAD dataset ID', 'Search string'), but these are minimal and don't fully explain semantics like valid dataset values or query formatting, leaving significant gaps.

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 for genes') and resource ('genes'), and specifies the API context ('gnomAD API'). However, it doesn't explicitly differentiate from sibling tools like 'search_for_variants' or 'get_gene_info', which would require a 5.

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 guidance on when to use this tool versus alternatives like 'search_for_variants' or 'get_gene_info' is provided. The description only lists parameters and returns without context about appropriate use cases or exclusions.

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