Skip to main content
Glama

get_str_info

Retrieve short tandem repeat (STR) information from the gnomAD v4 database using a reference genome and STR identifier to analyze genetic variations.

Instructions

[gnomAD API] Retrieve STR info (v4 only) Args: reference_genome (str): Reference genome (GRCh38) id (str): STR ID (e.g. ATXN1) Returns: dict: STR info Note: Not supported in v2/v3.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reference_genomeYes
idYes
datasetNognomad_r4

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function `get_str_info` implements the tool logic for retrieving short tandem repeat information. It validates the dataset version and uses `run_query_with_metadata` to execute the query.
    def get_str_info(
        reference_genome: str,
        id: str,
        dataset: str = 'gnomad_r4'
    ) -> dict:
        """
        [gnomAD API] Retrieve STR info (v4 only)
        Args:
            reference_genome (str): Reference genome (GRCh38)
            id (str): STR ID (e.g. ATXN1)
        Returns:
            dict: STR info
        Note:
            Not supported in v2/v3.
        """
    
        if dataset != 'gnomad_r4':
            raise ValueError("Only v4 is supported for STR info.")
    
        variables = {
            'dataset': dataset,
            'reference_genome': reference_genome,
            'id': id,
        }
        return run_query_with_metadata('short_tandem_repeat', variables)
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 API source and version constraints, but lacks details on authentication needs, rate limits, error handling, or what the 'STR info' dict typically contains (e.g., fields like allele frequencies). For a read operation with zero annotation coverage, this leaves significant gaps in understanding tool behavior.

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 well-structured with sections (Args, Returns, Note) and front-loaded the core purpose. It's concise with no wasted words, though the omission of the 'dataset' parameter slightly affects completeness. Every sentence adds value, such as the version warning and parameter examples.

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 the tool's moderate complexity (3 parameters, no annotations, but with an output schema), the description is partially complete. It covers the purpose and key parameters but misses details on the undocumented 'dataset' param and behavioral aspects like auth or errors. The output schema exists, so describing return values isn't needed, but other gaps remain for adequate agent use.

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 0%, so the description must compensate. It documents two parameters ('reference_genome' and 'id') with examples and notes, adding meaning beyond the bare schema. However, it omits the third parameter 'dataset' entirely, which has a default value 'gnomad_r4'—this gap reduces effectiveness. The description provides partial but incomplete parameter semantics.

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: 'Retrieve STR info' from the gnomAD API, specifying it's for 'v4 only'. It distinguishes from siblings by focusing on STR (short tandem repeat) data, unlike gene/variant tools. However, it doesn't explicitly contrast with all siblings (e.g., 'get_region_info' might overlap).

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 some usage context via the 'Note' about version support ('Not supported in v2/v3'), implying when not to use it. It doesn't explicitly guide when to choose this over similar tools (e.g., 'get_region_info' for broader genomic regions) or mention prerequisites like API access. The guidance is implied but not comprehensive.

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