Skip to main content
Glama

generate_sequence

Generate continuous DNA sequences from a starting prompt using the Evo 2 language model. Controls diversity with temperature and top-k sampling.

Instructions

Generate DNA sequence continuation using Evo 2.

Generates new DNA sequence tokens conditioned on a given prompt sequence using the Evo 2 language model. The generation process uses nucleus sampling (top-k) for controlled diversity.

Args: prompt: Starting DNA sequence to condition generation. Should contain standard IUPAC nucleotides (A, C, G, T, N). checkpoint: Model checkpoint identifier. If None, uses the default checkpoint. See list_available_checkpoints() for available options. n_tokens: Number of new tokens to generate. Must be a positive integer. temperature: Sampling temperature controlling randomness. Higher values (>1.0) increase diversity; lower values (<1.0) make generation more deterministic. Must be greater than 0. top_k: Number of highest probability nucleotides to sample from at each step. Must be positive. Typical values: 5 (all nucleotides including N), 4 (more constrained).

Returns: Dictionary containing: - checkpoint: The checkpoint identifier used - prompt: The normalized input prompt sequence - generated_sequence: The newly generated DNA sequence - n_tokens: Number of tokens generated - temperature: Temperature value used - top_k: Top-k value used

Raises: AssertionError: If prompt is empty, n_tokens <= 0, temperature <= 0, or top_k <= 0.

Example: >>> result = generate_sequence("ATCGATCG", n_tokens=100, temperature=0.8) >>> full_sequence = result["prompt"] + result["generated_sequence"] >>> print(f"Generated sequence: {full_sequence}")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_kNo
promptYes
n_tokensNo
checkpointNo
temperatureNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/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 details the sampling method (nucleus sampling with top-k), parameter effects, assertion errors for invalid inputs, and the normalization of the prompt. It does not explicitly state that the operation is read-only, but the generation nature implies no side effects.

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 well-structured with a clear one-liner purpose followed by detailed Args, Returns, Raises, and Example sections. Every sentence adds value, and the front-loading of the main purpose makes it easy to scan. It is appropriately sized for a complex generation tool.

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?

Despite the lack of annotations, the description provides comprehensive coverage: a clear purpose, detailed parameter semantics, expected return structure, error conditions, and a usage example. The output schema is not shown but the Returns section fully documents the dictionary keys. This is complete enough for an agent to invoke the tool correctly without further context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate, and it does thoroughly. Each parameter is explained with constraints, default behavior, and examples (e.g., top_k typical values). The Args section adds significant meaning beyond the raw schema types and defaults.

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 clearly states the tool's purpose with a specific verb and resource: 'Generate DNA sequence continuation using Evo 2.' It distinguishes from sibling tools by focusing on sequence generation rather than scoring or embedding. The example further clarifies the intended use.

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?

The description provides clear context for when to use this tool (generating sequence continuations) and references a sibling function `list_available_checkpoints()` for finding valid checkpoints. However, it does not explicitly state when not to use this tool versus alternatives, though the focused purpose makes the primary use case obvious.

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/not-a-feature/evo2-mcp'

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