Skip to main content
Glama
rcsb

io.github.rcsb/rcsb-mcp

Official
by rcsb

rcsb_search_strucmotif

Read-onlyIdempotent

Search for structures sharing a specific 3D residue arrangement (structural motif) from a reference entry, enabling discovery of catalytic sites, binding pockets, or metal-coordination geometries.

Instructions

Find structures containing a 3D STRUCTURAL MOTIF — a geometric arrangement of specific residues — like the one in a reference structure.

This is geometry-based and DIFFERENT from rcsb_search_by_structure (whole-shape similarity) and from rcsb_search_by_seqmotif (sequence pattern). Use it for catalytic triads, binding sites, metal-coordination geometries, etc.

Args: entry_id: Reference PDB entry defining the motif, e.g. "2MNR". residue_ids: 2-10 residues defining the motif, each a dict {"label_asym_id": , "label_seq_id": , "struct_oper_id"?: }. IMPORTANT: these are the mmCIF label identifiers (the internal numbering), which often DIFFER from the author residue numbers seen in papers/the PDB site. If you only have author numbering, resolve the label_asym_id/label_seq_id first (e.g. via rcsb_get_polymer_entity_instances) — author numbers give wrong/no hits. Example (enolase catalytic residues): [{"label_asym_id":"A","label_seq_id":162}, {"label_asym_id":"A","label_seq_id":193}, {"label_asym_id":"A","label_seq_id":219}] backbone_distance_tolerance: Backbone distance tolerance in Å, integer 0-3 (default 1). side_chain_distance_tolerance: Side-chain distance tolerance in Å, integer 0-3 (default 1). angle_tolerance: Angle tolerance in multiples of 20°, integer 0-3 (default 1). rmsd_cutoff: Maximum RMSD of accepted hits (default 2.0). atom_pairing_scheme: ALL, BACKBONE, SIDE_CHAIN (default), or PSEUDO_ATOMS. motif_pruning_strategy: NONE or KRUSKAL (default). return_type: What to return (default "assembly"); see the "Return types and fetching details" note in the server instructions. limit: Max hits (1-100). offset: Number of hits to skip, for paging; pass the response's next_offset back with the same query to fetch the next page. all_hits: Return the COMPLETE result set in one call (for an explicit "ALL ..." request); ignores limit, can't be combined with offset, and is refused above 10000 hits. Ignored when facets is set. attributes: Optional structured filters AND/OR-combined with this match — a list of AttributeFilter {attribute, operator, value, negation?, case_sensitive?} (e.g. restrict to an organism or resolution). See rcsb_search_by_attribute / rcsb_list_pdb_search_attributes for paths and operators. logical_operator: Combine this match and the attribute conditions with "and" (default) or "or". facets: Optional aggregation specs to return a breakdown / distribution instead of hits (see the faceting note in the server instructions for the spec). group_by, group_by_ranking: Collapse redundant polymer_entity hits into clusters, one representative each (needs return_type="polymer_entity") — see the grouping note in the server instructions. sort_by: Attribute path to order the hits by, replacing the default score ordering (each hit's score is still returned); omit to keep it. Only SORTABLE attributes work: those listing exact_match (strings) or equals (numbers/dates) in rcsb_list_pdb_search_attributes; full-text-only attributes (e.g. struct.title) and return_type="mol_definition" are rejected. sort_direction: "asc" (default) or "desc"; applies only when sort_by is set.

Returns: {total_count, returned, offset, has_more, next_offset, hits:[{id, score}], editor}; with facets, instead returns {total_count, facets, editor}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
facetsNo
offsetNo
sort_byNo
all_hitsNo
entry_idYes
group_byNo
attributesNo
residue_idsYes
return_typeNoassembly
rmsd_cutoffNo
sort_directionNoasc
angle_toleranceNo
group_by_rankingNo
logical_operatorNoand
atom_pairing_schemeNoSIDE_CHAIN
motif_pruning_strategyNoKRUSKAL
backbone_distance_toleranceNo
side_chain_distance_toleranceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

The description provides rich behavioral context beyond the annotations (readOnlyHint, openWorldHint, idempotentHint): it warns that author residue numbers give wrong/no hits, explains the all_hits behavior for explicit ALL requests, notes pagination with next_offset, and specifies sort_by restrictions (only sortable attributes, mol_definition rejected). This goes far beyond the static annotations and helps the agent anticipate edge cases.

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 into purpose, differences, Args, and Returns, and every sentence adds value. It is long due to 19 parameters, but avoids redundancy and uses efficient formatting (bold labels, examples, inline cautions). No fluff or repetition of schema defaults that are already visible.

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 high complexity (19 parameters, no schema descriptions, subtle return types), the description is exhaustive. It covers all parameters, provides return format details (including the facets variant), and warns about pitfalls like author numbering and sort restrictions. This is a complete standalone reference for correct invocation.

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?

Despite a 0% schema description coverage, the description compensates thoroughly. It explains residue_ids format with a concrete example (enolase catalytic residues), defines tolerance units and defaults, details all_hits/limit/offset interaction, and clarifies attributes, facets, group_by, and sort_by semantics. This is exactly the compensation needed for an under-documented 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 explicitly states the tool finds structures containing a 3D structural motif, defined as a geometric arrangement of specific residues. It clearly distinguishes this from rcsb_search_by_structure (whole-shape similarity) and rcsb_search_by_seqmotif (sequence pattern), making its unique role unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('catalytic triads, binding sites, metal-coordination geometries') and explicitly differentiates it from two sibling tools, naming them directly. It also provides practical guidance on resolving label vs author numbering, which is essential context for correct usage.

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/rcsb/rcsb-mcp'

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