Skip to main content
Glama

Motif Scan

seq_motif_scan
Read-onlyIdempotent

Scan nucleotide sequences for IUPAC motif occurrences, supporting ambiguous bases and bracket groups. Control overlapping match reporting with a simple parameter.

Instructions

Scan a nucleotide sequence for IUPAC motif occurrences (supports bracket groups).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
motifYesIUPAC motif to search for, optionally with bracket groups (e.g. 'ATG[AC]' matches ATGA and ATGC). Valid: A,C,G,T,U,R,Y,S,W,K,M,B,D,H,V,N.
sequenceYesNucleotide sequence (DNA or RNA; case-insensitive). IUPAC ambiguity codes (R, Y, S, W, K, M, B, D, H, V, N) are accepted where documented.
max_matchesNoCap on the number of matches reported. When the cap is reached the result's truncated flag is True and the reported matches are a prefix; narrow the motif or set overlapping=False for the full set.
overlappingNoIf True, report overlapping matches (next scan starts at the next base); if False, scan greedily left-to-right.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
motifYesThe motif searched for (uppercased).
matchesYesMatch positions (empty when the motif is not found).
sequenceYesThe input nucleotide sequence (uppercased).
truncatedNoTrue when the match cap (max_matches) was reached and the reported matches are a prefix of the full result set. Narrow the motif or set overlapping=False to get all matches.
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the bar is lower. The description adds useful behavioral context, notably the support for IUPAC codes and bracket groups, which are not in the annotations. It does not describe edge cases like truncation, but schema parameters cover those, making this a solid 4.

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 a single, front-loaded sentence that conveys the core action and a key capability. There is zero wasted prose, and it earns a perfect score for conciseness and structure.

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?

With a detailed input schema (100% coverage), informative annotations, and an output schema present, the brief description is sufficient. It supplies the high-level purpose while the schema and annotations handle parameter semantics and safety, making the overall tool definition 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%, with detailed parameter descriptions for motif, sequence, max_matches, and overlapping. The tool description itself adds no new parameter meaning beyond the schema, so the baseline score of 3 applies.

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 'Scan a nucleotide sequence for IUPAC motif occurrences (supports bracket groups)' uses a specific verb and resource, clearly distinguishing this tool from sequence-statistics or transformation siblings. It also highlights the distinctive bracket-group feature, making the purpose unambiguous.

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 context clearly implies use for finding motif occurrences in nucleotide sequences, and the sibling tool names (e.g., seq_gc_content, seq_reverse_complement) make alternatives obvious. However, the description does not explicitly state when not to use this tool or name alternatives, so it stops short of a 5.

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/madhusudan-kulkarni/biotools-mcp'

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