Skip to main content
Glama

print_ribbon_view

Convert your structure into a 3D-printable solid: thick ribbons plus a continuous backbone spine fuse to create a gap-free, rigid model for FDM printing.

Instructions

Chunky β-arrow ribbons plus a continuous backbone "spine", tuned for rigid, gap-free 3D printing.

Configures the look developed for FDM printing: thick β-strand arrows and a fat helix on the main object with loop cartoon hidden, plus a separate <obj>_spine object showing PyMOL's cartoon tube (which ignores secondary structure) running unbroken through the whole backbone. The spine threads through the strand bodies, so when the two objects are exported together the voxel step fuses them into ONE watertight solid with no strand→loop discontinuity. The spine also acts as internal rebar, reinforcing the thin junctions for print rigidity.

After calling this, export the fused solid with::

print_export(obj_name="<obj>",
              groups="<obj>=(<obj> or <obj>_spine)",
              representation="cartoon",
              method="voxel", voxel_pitch=0.2)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
obj_nameYesPyMOL object name (e.g. "1abc").
spine_radiusNoRadius (A) of the continuous backbone tube. Larger values give more internal reinforcement. Default 0.9.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully carries the burden of behavioral disclosure. It details that a separate `<obj>_spine` object is created, loop cartoon is hidden, the spine threads through strand bodies, and the two objects fuse into one watertight solid for export. It also explains the spine acts as internal rebar. This is rich, non-obvious behavior that goes well beyond basic expectations.

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 description is somewhat long but structured: opening summary, mechanism explanation, and a code block for the next step. Each sentence contributes useful context about the 3D-printing design. It is not overly verbose, and the structure aids comprehension. The code block is a helpful formatting choice for the follow-up step.

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?

Despite having an output schema (per context signals), the description covers the complete workflow: what the tool does, why it is needed, how the objects fuse, and the exact export command. It is self-contained and leaves no critical gaps for a user intending to prepare a printable PDB visualization.

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%, so the baseline is 3. The description adds contextual background (e.g., the spine acts as rebar) but does not add new parameter syntax or meaning beyond the schema. The schema already explains the radius and its default; the description's extra detail is tangential rather than directly illuminating parameter semantics.

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 opens with a specific verb+resource: "Chunky β-arrow ribbons plus a continuous backbone 'spine', tuned for rigid, gap-free 3D printing." It clearly distinguishes this from sibling view tools by focusing on 3D printing preparation, and it explicitly names the companion tool (print_export) needed to complete the workflow.

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 a clear usage context: it configures the look for FDM printing and then instructs to export with print_export. It implies when to use it (before print_export) but does not explicitly state exclusions or alternatives. The workflow statement "After calling this, export the fused solid with: print_export(...)" gives practical guidance, but lacks a direct 'use this instead of X' comparison.

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/chemrich/MCPymol'

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