Skip to main content
Glama

jean — Molecular Biology & Genomics

apply_variant_call

Read-only

Substitute one called ALT allele into a sequence and return the edited bases, the range the edit occupies and the length change. The REF allele is checked against the sequence first and a mismatch REFUSES naming both: applying a call from a different assembly would produce a construct that looks fine and is wrong. Symbolic and breakend alleles are refused for what they are: they name a rearrangement rather than replacement bases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
posYesthe POS of the record to apply, 1-based as VCF writes it.
fileNowhich call set the variant comes from, by name. Unset, it is the project's only one.
_filesNoThe project: record references shaped like _subject. Their records become library documents a tool names in sequences/parts/document; a trace or alignment is found by file name.
contigYesthe contig of the record to apply, as the file names it.
offsetNothe coordinate this sequence's FIRST base has in the call set's contig. Default 1, meaning the sequence starts at the contig's start. A plasmid extracted from a genome sets this to where it was cut from, which is what lets a genomic call be applied to it at all.
_subjectNoThe record to act on: exactly one of sequence, accession (+source), sample (an id from list_samples) or file ({name, text} or {name, base64}); record_index picks one record of several.
sequenceYesthe sequence to edit.
alt_indexNowhich ALT of a multiallelic record to apply, counting from 1 as the file lists them. Default the first.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
deltaYessigned length change, which is what any annotation downstream of the edit must shift by
appliedYesthe record as applied: chrom, pos, ref, the ALT chosen and its index, so a run record says which allele of a multiallelic site was taken
summaryYesthe edit in one sentence, generated from this run
sequenceYesthe sequence with this ALT substituted for the REF, ready to wire into a next step. Every base outside the edited range is unchanged, and the length differs from the input by `delta`, so any coordinate downstream of `edited_start` has moved by that much
edited_endYes0-based INCLUSIVE end of the edited range in the new sequence. Inclusive, not half-open, because it is the end of a selection a reader is meant to see highlighted rather than a slice bound
edited_startYes0-based inclusive start of the range the edit occupies in the NEW sequence, for selecting it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the read-only annotations, the description discloses important behavior: it returns edited bases, the edit range, and length change; it checks REF and refuses mismatch while naming both alleles; and it refuses symbolic and breakend alleles with reasons. These are valuable failure modes and validation semantics. It does not cover every edge case, but it adds substantial behavioral context beyond the structured annotations.

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

Conciseness5/5

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

The description is three tightly written sentences. It front-loads the operation and return values, then adds the REF validation rule, then the symbolic/breakend refusal. Every sentence carries distinct, useful information with no waste.

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

Completeness4/5

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

Given the output schema and the detailed input schema, the description covers purpose, core behavior, validation, and return values. Safety annotations already cover read-only status. The main gap is that it does not help the agent route between this tool and related siblings, but for calling the tool correctly it is largely complete.

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 parameter schemas already document each field, including offset, alt_index, and _subject. The description adds conceptual context about REF/ALT matching and assembly consistency but does not add parameter-level syntax or meaning beyond the schema. Per the rubric, the baseline is 3 when the schema does the heavy lifting.

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 states a specific verb and resource: 'Substitute one called ALT allele into a sequence' and returns the edited bases, edit range, and length change. This is clear enough for an agent to understand the operation. However, it does not explicitly distinguish the tool from related siblings such as read_variant_calls or score_variant_effect, so it falls short of 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 Guidelines3/5

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

The description gives implied usage conditions: the REF allele must match the sequence, and symbolic or breakend alleles are refused. This tells an agent when the tool is applicable and when it will fail. It does not, however, name alternatives or contrast the tool with sibling tools, so it remains only implied guidance.

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.

Resources