Skip to main content
Glama

Assembly

assembly
Read-onlyIdempotent

"Biological assembly of [pdb_id]" / "functional oligomer for [PDB entry]", fetch a biological assembly record (the functional oligomeric unit, which often differs from the crystallographic asymmetric unit). Use when you need the actual functional form of a protein (dimer / tetramer / etc.) rather than the crystal contents.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pdb_id": "1abc"
    },
    "name": "assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
pdb_idYes
assembly_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuine domain context — that assemblies can differ from the deposited asymmetric unit — but says nothing about multiple assemblies per entry, what happens when assembly_id is omitted, or how failures surface.

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

Conciseness4/5

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

The core sentence is front-loaded and dense with useful distinctions, with no padding sentences. The leading quoted title fragments ("Biological assembly of [pdb_id]" / "functional oligomer for [PDB entry]") are redundant boilerplate that add little.

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

Completeness3/5

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

With an output schema present, return values need not be explained, and the read-only annotations reduce the behavioral burden. The remaining gap is real, though: for a two-parameter tool where one parameter is undocumented anywhere, an agent has no basis for choosing an assembly_id.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning and it does not. "[pdb_id]" merely restates the identifier's name, and assembly_id — the parameter that actually determines which of several assemblies is returned — is never mentioned, leaving its format, default, and selection logic undocumented.

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 uses a specific verb ("fetch") and a precisely named resource ("a biological assembly record"), then defines it as the functional oligomeric unit that often differs from the crystallographic asymmetric unit. This conceptually separates it from structure-retrieval siblings without naming them, so an agent understands what it gets but must infer the boundary against rcsb_pdb_structure on its own.

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?

It gives a clear selection rule: "Use when you need the actual functional form of a protein (dimer / tetramer / etc.) rather than the crystal contents." That is an explicit use case plus an implicit exclusion (crystal contents), but it never names an alternative tool or states when not to call it.

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.