Skip to main content
Glama

print_ribbon_view

Configures PyMOL objects with chunky beta-arrow ribbons and a continuous backbone spine, producing gap-free 3D printable solids with internal reinforcement.

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)

Args: obj_name: PyMOL object name (e.g. "1abc"). spine_radius: Radius (A) of the continuous backbone tube. Larger values give more internal reinforcement. Default 0.9.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
obj_nameYes
spine_radiusNo

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 discloses the tool's behavior: it modifies cartoon settings, creates a separate spine object, and fuses them for printing. It also notes the spine's rebar effect and the need for export.

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 well-structured with purpose, behavior, example, and parameters. It is slightly lengthy but each sentence adds value; minor trimming could improve conciseness.

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 complexity and the presence of an output schema (though not shown), the description covers all necessary aspects: purpose, behavioral impact, parameter details, and usage example. No gaps remain.

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?

The description's Args section adds significant meaning beyond the schema, explaining the role of obj_name and the default/effect of spine_radius. Schema coverage is 0%, so the description fully compensates.

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 defines the tool's purpose: configuring a ribbon view optimized for 3D printing, with specific details on the spine and fusion. It distinguishes from siblings by focusing on printing-specific setup, not general display.

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 explains when to use the tool (for FDM printing) and provides an example of subsequent export. However, it does not explicitly state when not to use or compare to alternatives, leaving some ambiguity.

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