center
Focus the PyMOL view on a specified selection of atoms or residues.
Instructions
Centers the view on a selection
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| selection | No | all |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Focus the PyMOL view on a specified selection of atoms or residues.
Centers the view on a selection
| Name | Required | Description | Default |
|---|---|---|---|
| selection | No | all |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description bears full responsibility for behavioral disclosure. It only states 'Centers the view', without explaining side effects (e.g., resetting rotation, affecting scale) or the meaning of 'selection' (e.g., atoms, objects). This is minimal transparency.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one sentence with no wasted words, but it is under-specified. Conciseness is positive, but the information is insufficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a view-centering tool, the description omits details about how 'selection' affects the operation (e.g., centering on atoms vs. objects) and does not explain viewport behavior. Though an output schema exists, the description remains incomplete for an agent to predict tool behavior accurately.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage, but the description adds only 'on a selection', without specifying valid values, format, or the effect of the default 'all'. It does not compensate for the schema's lack of documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Centers the view on a selection'. It clearly indicates the tool's action, but does not differentiate from siblings like 'orient', 'zoom', or 'reset', which also manipulate the viewpoint.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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