Skip to main content
Glama

cartoon

Set the visual representation style for a protein selection in PyMOL, choosing from automatic, tube, loop, rectangle, oval, arrow, dumbbell, putty, or skip.

Instructions

Sets the cartoon type for the specified selection

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_typeYesCartoon style: ``automatic``, ``tube``, ``loop``, ``rectangle``, ``oval``, ``arrow``, ``dumbbell``, ``putty``, ``skip``. ``tube`` ignores secondary structure and runs unbroken through the backbone.
selectionNoPyMOL selection string, e.g. "1abc and chain A". See the module note for syntax.all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior1/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It simply states 'Sets the cartoon type' without mentioning side effects, reversibility, or what happens to existing cartoon settings. The tool's mutating behavior is implied but never elaborated.

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 a single, front-loaded sentence with no redundant or extraneous information. Every word contributes to the core purpose, making it highly concise and well-structured.

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?

The tool is simple with a rich input schema and an output schema, yet the description lacks any usage context or exclusionary guidance. It is adequate for a minimal tool but does not fully address the broader context of when or how to use it beyond the literal action.

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 coverage is 100%, so the input schema already provides detailed descriptions for both parameters (item_type and selection). The tool description adds nothing beyond the schema, so the baseline score of 3 is appropriate.

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 'Sets the cartoon type for the specified selection' uses a specific verb ('sets') and resource ('cartoon type'), clearly distinguishing it from sibling tools like 'show', 'set', or 'as'. The target 'selection' is also specific, leaving no ambiguity about the tool's function.

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

Usage Guidelines2/5

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

No guidance is given on when to use cartoon versus alternative representations or how it relates to other tools. The description is purely declarative and offers no exclusions, prerequisites, or comparisons to siblings, leaving the agent without usage context.

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