Skip to main content
Glama
Sign In
MCPymol

MCPymol

by chemrich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

refresh

Idempotent

Updates the PyMOL display so current scene changes are visible, ensuring the viewer matches the current model state.

Instructions

Refreshes the display

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": "refresh"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare non-destructive, idempotent behavior and explicitly mark it as not read-only, which the description is consistent with. Beyond that the description adds nothing: it does not say what state is refreshed, whether camera or scene settings are affected, or whether any pending changes are flushed.

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?

A single short sentence with the action front-loaded and no filler. It is appropriately sized for a zero-parameter command, though the brevity reflects under-specification as much as economy.

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 trivially simple, has no parameters, and ships an output schema, so return values need no prose. What is missing is any statement of the effect on the viewer state or when the call is warranted, leaving the definition only minimally usable.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline applies. The empty schema is self-explanatory and the description does not need to compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Refreshes the display" gives a verb and an object, so the basic action is identifiable, but "display" is undefined and nothing distinguishes it from siblings such as viewport, full_screen, or rock that also affect what is on screen. An agent can guess it redraws the current view, but must infer that.

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?

There is no statement of when to call this versus alternatives, no preconditions, and no mention of when a refresh is unnecessary or already implied by another command. Usage must be inferred entirely from the name.

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