Skip to main content
Glama

gnomad-genetics-mcp-server

gnomad-genetics-mcp-server: get coverage

gnomad_get_coverage
Read-onlyIdempotent

Fetch gnomAD sequencing-coverage summary across a gene, transcript, or region — mean and median read depth, plus the mean fraction of samples covered at each depth threshold (1× through 100×), separated by exome and genome track. gnomAD reports coverage in buckets: 1 bp for a region spanning under 850 bp, wider for larger targets (bucket_size), and a gene or transcript is summarized over its exons ±75 bp, not its introns. Use this to disambiguate a true absent variant from an uncallable position: a variant missing from a well-covered region is informative, while one missing from a poorly-covered region is not. Supply exactly one of gene, transcript_id, or region. The optional coverage_source narrows to one track; by default both available tracks are returned. gnomAD publishes no coverage for subsets, so a subset dataset reads its parent release (gnomad_r4_non_ukb reads gnomad_r4) over all the parent’s samples: coverage_dataset names the release read, and a notice says so. Echoes the effective dataset and build. Data source: gnomAD (Broad Institute) — https://gnomad.broadinstitute.org/

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gnomad_get_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneNoGene — HGNC symbol (e.g. PCSK9) or Ensembl gene ID (e.g. ENSG00000169174). Obtain a stable ID from ensembl_lookup_gene. Mitochondrial genes (e.g. MT-TL1) are not served. Mutually exclusive with transcript_id and region; blank means omitted.
regionNoGenomic region chrom-start-stop (1-based inclusive, e.g. 1-55039447-55064852): chromosome 1–22, X, or Y with an optional chr prefix (mitochondrial regions are not served) and a span (stop − start) under 2,500,000 bp. Mutually exclusive with gene and transcript_id.
datasetNognomAD dataset, default gnomad_r4: gnomad_r4 and its subset gnomad_r4_non_ukb (GRCh38); gnomad_r3 and its subsets gnomad_r3_controls_and_biobanks, gnomad_r3_non_cancer, gnomad_r3_non_neuro, gnomad_r3_non_topmed, gnomad_r3_non_v2 (GRCh38); gnomad_r2_1 and its subsets gnomad_r2_1_controls, gnomad_r2_1_non_cancer, gnomad_r2_1_non_neuro, gnomad_r2_1_non_topmed (GRCh37); exac (GRCh37). A subset keeps only part of its parent release's samples (non_cancer leaves out cancer-study samples, non_ukb UK Biobank's) and can leave a callset unchanged: gnomad_r4_non_ukb genome counts equal gnomad_r4's, and gnomad_r2_1_non_cancer genome counts equal gnomad_r2_1's. No subset publishes joint data, and gnomAD publishes no subset coverage or constraint, so those come from the parent. Echoed in output.
transcript_idNoEnsembl transcript ID (e.g. ENST00000302118). Mutually exclusive with gene and region; blank means omitted.
coverage_sourceNoRestrict to one coverage track. Omit to return every available track.
reference_genomeNoReference build. Derived from dataset when omitted: GRCh38 for gnomad_r4, gnomad_r3, and their subsets; GRCh37 for gnomad_r2_1, its subsets, and exac. If supplied it must match the dataset, or the call is rejected. Keep aligned with ensembl coordinates.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
noticeNoDisclosure that a subset dataset was read from its parent release, and of missing target bases, missing supported tracks, or an explicitly requested unsupported track. Missing data leaves callability unknown.
targetNoThe resolved target (gene symbol/ID, transcript ID, or region) the coverage describes.
datasetNoEffective gnomAD dataset.
summariesNoPer-track coverage summaries (exome and/or genome).
target_kindNoWhich target type was queried.
coverage_datasetNoThe gnomAD release the coverage was read from: dataset itself for a release, the parent release for a subset (gnomad_r4 for gnomad_r4_non_ukb, gnomad_r3 for the gnomad_r3 subsets, gnomad_r2_1 for the gnomad_r2_1 subsets), since gnomAD publishes no subset coverage.
reference_genomeNoEffective reference build.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / dataset / description
      Previous value: -"gnomAD dataset: gnomad_r4 (GRCh38, default), gnomad_r3 (GRCh38), gnomad_r2_1 (GRCh37), exac (GRCh37). Echoed in output."New value: +"gnomAD dataset, default gnomad_r4: gnomad_r4 and its subset gnomad_r4_non_ukb (GRCh38); gnomad_r3 and its subsets gnomad_r3_controls_and_biobanks, gnomad_r3_non_cancer, gnomad_r3_non_neuro, gnomad_r3_non_topmed, gnomad_r3_non_v2 (GRCh38); gnomad_r2_1 and its subsets gnomad_r2_1_controls, gnomad_r2_1_non_cancer, gnomad_r2_1_non_neuro, gnomad_r2_1_non_topmed (GRCh37); exac (GRCh37). A subset keeps only part of its parent release's samples (non_cancer leaves out cancer-study samples, non_ukb UK Biobank's) and can leave a callset unchanged: gnomad_r4_non_ukb genome counts equal gnomad_r4's, and gnomad_r2_1_non_cancer genome counts equal gnomad_r2_1's. No subset publishes joint data, and gnomAD publishes no subset coverage or constraint, so those come from the parent. Echoed in output."
    • changedInput schema / properties / dataset / enum
      Previous value: -[
      -  "gnomad_r4",
      -  "gnomad_r3",
      -  "gnomad_r2_1",
      -  "exac"
      -]New value: +[
      +  "gnomad_r4",
      +  "gnomad_r4_non_ukb",
      +  "gnomad_r3",
      +  "gnomad_r3_controls_and_biobanks",
      +  "gnomad_r3_non_cancer",
      +  "gnomad_r3_non_neuro",
      +  "gnomad_r3_non_topmed",
      +  "gnomad_r3_non_v2",
      +  "gnomad_r2_1",
      +  "gnomad_r2_1_controls",
      +  "gnomad_r2_1_non_neuro",
      +  "gnomad_r2_1_non_cancer",
      +  "gnomad_r2_1_non_topmed",
      +  "exac"
      +]
    • changedInput schema / properties / reference_genome / description
      Previous value: -"Reference build. Derived from dataset when omitted (v4/v3=GRCh38, v2.1/ExAC=GRCh37). If supplied it must match the dataset, or the call is rejected. Keep aligned with ensembl coordinates."New value: +"Reference build. Derived from dataset when omitted: GRCh38 for gnomad_r4, gnomad_r3, and their subsets; GRCh37 for gnomad_r2_1, its subsets, and exac. If supplied it must match the dataset, or the call is rejected. Keep aligned with ensembl coordinates."
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "not": {
      -      "required": [
      -        "error"
      -      ]
      -    },
      -    "required": [
      -      "target",
      -      "target_kind",
      -      "summaries",
      -      "dataset",
      -      "reference_genome"
      -    ]
      -  },
      -  {
      -    "required": [
      -      "error"
      -    ]
      -  }
      -]New value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "target",
      +      "target_kind",
      +      "summaries",
      +      "dataset",
      +      "coverage_dataset",
      +      "reference_genome"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / coverage_dataset
      Added value: +{
      +  "description": "The gnomAD release the coverage was read from: dataset itself for a release, the parent release for a subset (gnomad_r4 for gnomad_r4_non_ukb, gnomad_r3 for the gnomad_r3 subsets, gnomad_r2_1 for the gnomad_r2_1 subsets), since gnomAD publishes no subset coverage.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / notice / description
      Previous value: -"Disclosure of missing target bases, missing supported tracks, or an explicitly requested unsupported track. Missing data leaves callability unknown."New value: +"Disclosure that a subset dataset was read from its parent release, and of missing target bases, missing supported tracks, or an explicitly requested unsupported track. Missing data leaves callability unknown."
  2. Changed2 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_target`: Not exactly one of gene, transcript_id, or region was supplied. `incoherent_build`: reference_genome was supplied but does not match the dataset. `invalid_region`: The region names a chromosome outside 1–22, X, Y, or breaks the coordinate bounds. `region_too_large`: The region spans 2,500,000 bp or more, beyond what gnomAD summarizes at once. `mitochondrial_unsupported`: The gene, transcript, or region is on the mitochondrial chromosome (M or MT). `graphql_error`: gnomAD rejected the coverage query with a GraphQL error. `upstream_unavailable`: gnomAD stayed unavailable or throttled through every retry. `upstream_timeout`: gnomAD attempts timed out or the shared 45 s call budget expired. `upstream_access`: gnomAD refused the request (access denied). `invalid_upstream_response`: gnomAD kept answering with a response that failed validation. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_target`: Not exactly one of gene, transcript_id, or region was supplied. `incoherent_build`: reference_genome was supplied but does not match the dataset. `invalid_region`: The region names a chromosome outside 1–22, X, Y, or breaks the coordinate bounds. `region_too_large`: The region spans 2,500,000 bp or more, beyond what gnomAD summarizes at once. `mitochondrial_unsupported`: The gene, transcript, or region is on the mitochondrial chromosome (M or MT). `gene_not_found`: gnomAD holds no gene matching the symbol or Ensembl ID in this build. `transcript_not_found`: gnomAD holds no transcript matching transcript_id in this build. `graphql_error`: gnomAD rejected the coverage query with a GraphQL error. `upstream_unavailable`: gnomAD stayed unavailable or throttled through every retry. `upstream_timeout`: gnomAD attempts timed out or the shared 45 s call budget expired. `upstream_access`: gnomAD refused the request (access denied). `invalid_upstream_response`: gnomAD kept answering with a response that failed validation. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_target",
      -  "incoherent_build",
      -  "invalid_region",
      -  "region_too_large",
      -  "mitochondrial_unsupported",
      -  "graphql_error",
      -  "upstream_unavailable",
      -  "upstream_timeout",
      -  "upstream_access",
      -  "invalid_upstream_response"
      -]New value: +[
      +  "invalid_target",
      +  "incoherent_build",
      +  "invalid_region",
      +  "region_too_large",
      +  "mitochondrial_unsupported",
      +  "gene_not_found",
      +  "transcript_not_found",
      +  "graphql_error",
      +  "upstream_unavailable",
      +  "upstream_timeout",
      +  "upstream_access",
      +  "invalid_upstream_response"
      +]
  3. Changed5 schema fields changed
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_target`: Not exactly one of gene, transcript_id, or region was supplied. `incoherent_build`: reference_genome was supplied but does not match the dataset. `invalid_region`: The region names a chromosome outside 1–22, X, Y, or breaks the coordinate bounds. `region_too_large`: The region spans 2,500,000 bp or more, beyond what gnomAD summarizes at once. `mitochondrial_unsupported`: The gene, transcript, or region is on the mitochondrial chromosome (M or MT). `graphql_error`: gnomAD rejected the coverage query with a GraphQL error. `upstream_unavailable`: gnomAD stayed unavailable or throttled through every retry. `upstream_timeout`: Every attempt to reach gnomAD timed out. `upstream_access`: gnomAD refused the request (access denied). `invalid_upstream_response`: gnomAD kept answering with a response that failed validation. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_target`: Not exactly one of gene, transcript_id, or region was supplied. `incoherent_build`: reference_genome was supplied but does not match the dataset. `invalid_region`: The region names a chromosome outside 1–22, X, Y, or breaks the coordinate bounds. `region_too_large`: The region spans 2,500,000 bp or more, beyond what gnomAD summarizes at once. `mitochondrial_unsupported`: The gene, transcript, or region is on the mitochondrial chromosome (M or MT). `graphql_error`: gnomAD rejected the coverage query with a GraphQL error. `upstream_unavailable`: gnomAD stayed unavailable or throttled through every retry. `upstream_timeout`: gnomAD attempts timed out or the shared 45 s call budget expired. `upstream_access`: gnomAD refused the request (access denied). `invalid_upstream_response`: gnomAD kept answering with a response that failed validation. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / notice / description
      Previous value: -"Guidance when no coverage data is available for the target."New value: +"Disclosure of missing target bases, missing supported tracks, or an explicitly requested unsupported track. Missing data leaves callability unknown."
    • addedOutput schema / properties / summaries / items / properties / missing_positions
      Added value: +{
      +  "description": "Target bases without returned coverage buckets (target_positions minus positions). Callability is unknown for these bases; they are not measured zero depth.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / summaries / items / properties / target_positions
      Added value: +{
      +  "description": "Total target bases: start..stop inclusive for a region, merged exons ±75 bp for a gene or transcript.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / summaries / items / required
      Previous value: -[
      -  "source",
      -  "positions",
      -  "bucket_count",
      -  "bucket_size",
      -  "mean_depth",
      -  "median_depth",
      -  "fraction_over_1",
      -  "fraction_over_5",
      -  "fraction_over_10",
      -  "fraction_over_15",
      -  "fraction_over_20",
      -  "fraction_over_25",
      -  "fraction_over_30",
      -  "fraction_over_50",
      -  "fraction_over_100"
      -]New value: +[
      +  "source",
      +  "positions",
      +  "target_positions",
      +  "missing_positions",
      +  "bucket_count",
      +  "bucket_size",
      +  "mean_depth",
      +  "median_depth",
      +  "fraction_over_1",
      +  "fraction_over_5",
      +  "fraction_over_10",
      +  "fraction_over_15",
      +  "fraction_over_20",
      +  "fraction_over_25",
      +  "fraction_over_30",
      +  "fraction_over_50",
      +  "fraction_over_100"
      +]
  4. Changed15 schema fields changed
    • addedOutput schema / properties / summaries / items / properties / bucket_count
      Added value: +{
      +  "description": "Number of gnomAD coverage buckets summarized: every returned bucket overlapping the target bases. gnomAD returns every bucket between the first and last record of a track, so an empty bucket inside that span counts as zero depth; buckets past the outermost records are not returned and not counted.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / summaries / items / properties / bucket_size
      Added value: +{
      +  "description": "Width of each gnomAD coverage bucket in bp: 1 for a region spanning under 850 bp, otherwise about 1/500 of the queried size. Depth and fraction values describe buckets, not single bases.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / summaries / items / properties / fraction_over_1 / description
      Previous value: -"Mean fraction of samples covered at ≥1×; null when no data."New value: +"Fraction of samples covered at ≥1×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_10 / description
      Previous value: -"Mean fraction of samples covered at ≥10×; null when no data."New value: +"Fraction of samples covered at ≥10×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_100 / description
      Previous value: -"Mean fraction of samples covered at ≥100×; null when no data."New value: +"Fraction of samples covered at ≥100×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_15 / description
      Previous value: -"Mean fraction of samples covered at ≥15×; null when no data."New value: +"Fraction of samples covered at ≥15×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_20 / description
      Previous value: -"Mean fraction of samples covered at ≥20×; null when no data."New value: +"Fraction of samples covered at ≥20×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_25 / description
      Previous value: -"Mean fraction of samples covered at ≥25×; null when no data."New value: +"Fraction of samples covered at ≥25×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_30 / description
      Previous value: -"Mean fraction of samples covered at ≥30×; null when no data."New value: +"Fraction of samples covered at ≥30×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_5 / description
      Previous value: -"Mean fraction of samples covered at ≥5×; null when no data."New value: +"Fraction of samples covered at ≥5×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / fraction_over_50 / description
      Previous value: -"Mean fraction of samples covered at ≥50×; null when no data."New value: +"Fraction of samples covered at ≥50×, averaged over the summarized buckets (gnomAD rounds each bucket's fraction up to the next 0.01); null when no data."
    • changedOutput schema / properties / summaries / items / properties / mean_depth / description
      Previous value: -"Mean read depth averaged across positions; null when no data."New value: +"Mean read depth: the average of the summarized buckets’ mean depths; null when no data."
    • changedOutput schema / properties / summaries / items / properties / median_depth / description
      Previous value: -"Median read depth across positions; null when no data."New value: +"Median, across the summarized buckets, of each bucket’s depth (the average of its per-base medians); null when no data."
    • changedOutput schema / properties / summaries / items / properties / positions / description
      Previous value: -"Number of base positions summarized across the target."New value: +"Target bases inside the summarized buckets: of start..stop for a region, of the exons ±75 bp for a gene or transcript. Falls short of the target when the track has no records at its edges (typically outside the exome capture); those bases are left out, not counted as zero depth."
    • changedOutput schema / properties / summaries / items / required
      Previous value: -[
      -  "source",
      -  "positions",
      -  "mean_depth",
      -  "median_depth",
      -  "fraction_over_1",
      -  "fraction_over_5",
      -  "fraction_over_10",
      -  "fraction_over_15",
      -  "fraction_over_20",
      -  "fraction_over_25",
      -  "fraction_over_30",
      -  "fraction_over_50",
      -  "fraction_over_100"
      -]New value: +[
      +  "source",
      +  "positions",
      +  "bucket_count",
      +  "bucket_size",
      +  "mean_depth",
      +  "median_depth",
      +  "fraction_over_1",
      +  "fraction_over_5",
      +  "fraction_over_10",
      +  "fraction_over_15",
      +  "fraction_over_20",
      +  "fraction_over_25",
      +  "fraction_over_30",
      +  "fraction_over_50",
      +  "fraction_over_100"
      +]
  5. Changed5 schema fields changed
    • changedInput schema / properties / gene / description
      Previous value: -"Gene — HGNC symbol (e.g. PCSK9) or Ensembl gene ID (e.g. ENSG00000169174). Obtain a stable ID from ensembl_lookup_gene. Mutually exclusive with transcript_id and region; blank means omitted."New value: +"Gene — HGNC symbol (e.g. PCSK9) or Ensembl gene ID (e.g. ENSG00000169174). Obtain a stable ID from ensembl_lookup_gene. Mitochondrial genes (e.g. MT-TL1) are not served. Mutually exclusive with transcript_id and region; blank means omitted."
    • changedInput schema / properties / region / anyOf
      Previous value: -[
      -  {
      -    "const": "",
      -    "type": "string"
      -  },
      -  {
      -    "description": "Genomic region chrom-start-stop (1-based inclusive, e.g. 1-55039447-55064852).",
      -    "pattern": "^[0-9XYM]+-\\d+-\\d+$",
      -    "type": "string"
      -  }
      -]New value: +[
      +  {
      +    "const": "",
      +    "type": "string"
      +  },
      +  {
      +    "description": "Genomic region chrom-start-stop (1-based inclusive, e.g. 1-55039447-55064852) on chromosome 1–22, X, or Y, optional chr prefix.",
      +    "pattern": "^(?:chr)?[0-9A-Z]+-\\d+-\\d+$",
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / region / description
      Previous value: -"Genomic region chrom-start-stop (1-based inclusive, e.g. 1-55039447-55064852). Mutually exclusive with gene and transcript_id."New value: +"Genomic region chrom-start-stop (1-based inclusive, e.g. 1-55039447-55064852): chromosome 1–22, X, or Y with an optional chr prefix (mitochondrial regions are not served) and a span (stop − start) under 2,500,000 bp. Mutually exclusive with gene and transcript_id."
    • changedOutput schema / properties / error / properties / data / properties / reason / description
      Previous value: -"Machine-readable failure mode. Declared by this tool: `invalid_target`: Not exactly one of gene, transcript_id, or region was supplied. `incoherent_build`: reference_genome was supplied but does not match the dataset. Other values are possible when a failure originates below the handler."New value: +"Machine-readable failure mode. Declared by this tool: `invalid_target`: Not exactly one of gene, transcript_id, or region was supplied. `incoherent_build`: reference_genome was supplied but does not match the dataset. `invalid_region`: The region names a chromosome outside 1–22, X, Y, or breaks the coordinate bounds. `region_too_large`: The region spans 2,500,000 bp or more, beyond what gnomAD summarizes at once. `mitochondrial_unsupported`: The gene, transcript, or region is on the mitochondrial chromosome (M or MT). `graphql_error`: gnomAD rejected the coverage query with a GraphQL error. `upstream_unavailable`: gnomAD stayed unavailable or throttled through every retry. `upstream_timeout`: Every attempt to reach gnomAD timed out. `upstream_access`: gnomAD refused the request (access denied). `invalid_upstream_response`: gnomAD kept answering with a response that failed validation. Other values are possible when a failure originates below the handler."
    • changedOutput schema / properties / error / properties / data / properties / reason / examples
      Previous value: -[
      -  "invalid_target",
      -  "incoherent_build"
      -]New value: +[
      +  "invalid_target",
      +  "incoherent_build",
      +  "invalid_region",
      +  "region_too_large",
      +  "mitochondrial_unsupported",
      +  "graphql_error",
      +  "upstream_unavailable",
      +  "upstream_timeout",
      +  "upstream_access",
      +  "invalid_upstream_response"
      +]
  6. Changed5 schema fields changed
    • addedInput schema / properties / gene / anyOf
      Added value: +[
      +  {
      +    "description": "Gene — HGNC symbol (e.g. PCSK9) or Ensembl gene ID (e.g. ENSG00000169174). Obtain a stable ID from ensembl_lookup_gene.",
      +    "minLength": 2,
      +    "type": "string"
      +  },
      +  {
      +    "description": "Blank — the gene is treated as omitted.",
      +    "maxLength": 0,
      +    "type": "string"
      +  }
      +]
    • changedInput schema / properties / gene / description
      Previous value: -"Gene — HGNC symbol (e.g. PCSK9) or Ensembl gene ID (e.g. ENSG00000169174). Obtain a stable ID from ensembl_lookup_gene."New value: +"Gene — HGNC symbol (e.g. PCSK9) or Ensembl gene ID (e.g. ENSG00000169174). Obtain a stable ID from ensembl_lookup_gene. Mutually exclusive with transcript_id and region; blank means omitted."
    • removedInput schema / properties / gene / minLength
      Removed value: -2
    • removedInput schema / properties / gene / type
      Removed value: -"string"
    • changedInput schema / properties / transcript_id / description
      Previous value: -"Ensembl transcript ID (e.g. ENST00000302118). Mutually exclusive with gene and region."New value: +"Ensembl transcript ID (e.g. ENST00000302118). Mutually exclusive with gene and region; blank means omitted."
  7. Changed22 schema fields changed
    • removedOutput schema / properties / summaries / items / properties / fraction_over_1 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_1 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_10 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_10 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_100 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_100 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_15 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_15 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_20 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_20 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_25 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_25 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_30 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_30 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_5 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_5 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / fraction_over_50 / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / fraction_over_50 / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / mean_depth / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / mean_depth / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedOutput schema / properties / summaries / items / properties / median_depth / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / summaries / items / properties / median_depth / type
      Added value: +[
      +  "number",
      +  "null"
      +]
  8. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses important behavioral traits: coverage is reported in buckets (1 bp for targets under 850 bp, wider for larger ones), genes/transcripts are summarized over exons ±75 bp and not introns, subsets read their parent release with a notice, and the effective dataset and build are echoed. These details materially affect how an agent interprets and trusts the returned coverage data.

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 front-loaded with the core purpose and remains logically organized through bucketing details, usage guidance, parameter constraints, and dataset caveats. It is dense but mostly earns its length; a small amount of repetition (e.g., subset-coverage behavior also documented in the dataset schema) keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (six parameters, three enums, an output schema, and open-world external data), the description is complete enough for correct invocation. It covers return semantics, usage rationale, track selection, dataset/build echoing, and subset-parent behavior, leaving no critical gap for an agent to call it properly.

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 already documents all six parameters thoroughly, including mutual exclusivity, dataset enums, and build derivation. The description reinforces a few points (default both tracks returned, subset datasets read parent coverage) but most of that is already present in the schema; the added meaning over structured fields is marginal, making baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Fetch gnomAD sequencing-coverage summary across a gene, transcript, or region') and enumerates the exact returned metrics (mean/median read depth, fraction covered at 1×–100×, separated by exome/genome track). It is clearly distinguishable from siblings like gnomad_get_variant or gnomad_get_gene_constraint without opening any schema.

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?

It gives an explicit when-to-use scenario: 'Use this to disambiguate a true absent variant from an uncallable position: a variant missing from a well-covered region is informative, while one missing from a poorly-covered region is not.' It also states the mutual-exclusivity constraint ('Supply exactly one of gene, transcript_id, or region'). However, it does not name alternative sibling tools or explicit when-not-to-use conditions, leaving the agent to infer that from tool names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.