Skip to main content
Glama

Draw a molecule

molecule
DestructiveIdempotent

Render a protein, DNA, or small-compound structure in 3D as a PNG plus a text summary; provide one PDB ID, local PDB file, or PDB text.

Instructions

Draw a protein, DNA or small molecule in 3D and return a PNG image plus a text summary.

When to use: to show one structure. To put a structure next to other charts, use a molecule panel in plot instead.

How: give exactly one source: pdb_id (a 4-character Protein Data Bank id such as 1UBQ), pdb_path (a local .pdb file) or pdb (the PDB text itself). The style defaults to cartoon for proteins and ball_and_stick otherwise; coloring defaults to element. rotate {x, y, z} turns the model by degrees; ramachandran adds a Ramachandran plot of the backbone angles.

Behavior: pdb_id downloads the structure from files.rcsb.org (the only network access); pdb_path only reads the file; nothing is written unless output is given. An unknown id, an unreadable file or PDB data without ATOM/HETATM records returns an error result whose text says which.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
pdbNoPDB file content.
imageNoReturn the image (default true; false returns only the text summary).
styleNoDrawing style (default cartoon for proteins, ball_and_stick otherwise).
themeNoColor theme (default light). high_contrast uses dark colors with at least 4.5:1 contrast and larger text.
titleNoFigure title.
widthNoWidth in pixels (default 900).
heightNoHeight in pixels (default 600).
outputNoAlso save the chart to this file path; the format follows the extension (.png, .svg, .pdf, or .html for an interactive page). An existing file at that path is overwritten. Omit to write nothing.
pdb_idNo4-character PDB id, e.g. 1UBQ.
rotateNoRotation in degrees about each axis, applied x, then y, then z.
coloringNoAtom colors: by element (default), by chain, or a rainbow along the chain.
pdb_pathNoPath of a local .pdb file to read.
ramachandranNoAdd a Ramachandran plot next to the structure.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / coloring / description
      Added value: +"Atom colors: by element (default), by chain, or a rainbow along the chain."
    • changedInput schema / properties / output / description
      Previous value: -"Also save the chart to this path (.png, .svg, .pdf or .html, interactive)."New value: +"Also save the chart to this file path; the format follows the extension (.png, .svg, .pdf, or .html for an interactive page). An existing file at that path is overwritten. Omit to write nothing."
    • addedInput schema / properties / pdb_path / description
      Added value: +"Path of a local .pdb file to read."
    • addedInput schema / properties / rotate / description
      Added value: +"Rotation in degrees about each axis, applied x, then y, then z."
    • addedInput schema / properties / style / description
      Added value: +"Drawing style (default cartoon for proteins, ball_and_stick otherwise)."
    • addedInput schema / properties / theme / description
      Added value: +"Color theme (default light). high_contrast uses dark colors with at least 4.5:1 contrast and larger text."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

The description goes well beyond the annotations by disclosing that pdb_id is the only network access, that nothing is written unless `output` is given, and which inputs produce error results with explanatory text. However, it never reconciles the annotation profile: destructiveHint=true and readOnlyHint=false are true only because of the optional `output` overwrite, and the description leaves that mapping implicit rather than stating it outright, so the safety picture is assembled by the reader rather than stated.

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?

Labelled 'When to use' / 'How' / 'Behavior' blocks make it scannable and the core purpose leads. It is slightly padded by repeating schema defaults (style, coloring fallbacks) that the agent can already read, costing a point.

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?

For a 13-parameter tool with a nested rotate object and no output schema, the description covers the return value, the image=false variant, the three mutually exclusive inputs, network vs local reads, write side effects, and error conditions. An agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3; the description earns a point by adding a constraint absent from the schema itself — 'give exactly one source' among pdb_id, pdb_path and pdb, which is not encoded as anyOf/oneOf. It also clarifies rotate ordering and the protein-vs-other style default, though those largely restate schema 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?

States a concrete verb and resource ('Draw a protein, DNA or small molecule in 3D') and names the outputs ('PNG image plus a text summary'), so the agent knows exactly what comes back without opening the schema.

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?

An explicit 'When to use' clause selects this tool for showing a single structure and routes multi-chart layouts to the sibling: 'to put a structure next to other charts, use a molecule panel in plot instead.' The alternative and its triggering condition are both named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools