Skip to main content
Glama

Sequence Similarity Search

science.pdb.sequence
Read-onlyIdempotent

Find PDB structures matching a protein sequence using BLAST. Configure identity cutoff and E-value to retrieve homologous chains for homology modeling and structure prediction.

Instructions

Search protein structures by amino acid sequence similarity (BLAST). Input a protein sequence and find all PDB structures with matching chains. Configure identity cutoff (e.g. 90%) and E-value threshold. Returns PDB entity IDs ranked by similarity score. Essential for homology modeling and structure prediction (RCSB PDB)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sequenceYesProtein amino acid sequence in one-letter code (e.g. "MVLSPADKTNVKAAWGKVGAHAGEYGAEALERMFLSFPTTKTYFPHFDLSH" — first 50 residues of human hemoglobin alpha)
identity_cutoffNoMinimum sequence identity (0.1-1.0). Default: 0.9 (90% identical)
evalue_cutoffNoMaximum E-value threshold for BLAST significance. Default: 0.1
limitNoMaximum number of results (1-50). Default: 10

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
Behavior4/5

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

Annotations already indicate safe read-only operation. The description adds behavioral context: uses BLAST, returns ranked PDB entity IDs, and configurable thresholds, which are not covered by 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 concise: two front-loaded sentences that state purpose, method, and output without extraneous information.

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 an output schema present, the description adequately explains the tool's purpose, parameters, and typical use case, making it complete for selection and invocation.

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 covers 100% of parameters with good descriptions. The tool description repeats some parameter info (e.g., identity cutoff, E-value) but does not add significant new semantics beyond the schema.

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 it searches protein structures by amino acid sequence similarity using BLAST, specifies input and output, and distinguishes from siblings like science.pdb.ligand and science.pdb.structure.

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 context for use (homology modeling, structure prediction) but does not explicitly state when not to use or mention alternatives to this tool.

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/whiteknightonhorse/APIbase'

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