Skip to main content
Glama
Sign In
MCPymol

MCPymol

by chemrich
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

mset

Idempotent

Defines frame-to-state mappings for movie playback so you can hold a state or sweep through states with precise animation control.

Instructions

Defines a sequence of states for movie playback

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "specification": "<specification>"
    },
    "name": "mset"
  }
}

Input Schema

NameRequiredDescriptionDefault
specificationYesFrame-to-state mapping, e.g. "1 x30" to hold state 1 for 30 frames, or "1 -30" to sweep states 1 through 30.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / specification / description
      Added value: +"Frame-to-state mapping, e.g. \"1 x30\" to hold state 1 for 30 frames, or \"1 -30\" to sweep states 1 through 30."
  2. 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 this is a non-read-only, idempotent, non-destructive write. The description adds only that it concerns movie playback states; it does not say whether an existing sequence is replaced, what preconditions exist, or how the sequence interacts with state definitions. Beyond the annotations, behavioral detail is thin.

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?

It is a single, front-loaded sentence with no wasted wording. It is perhaps too terse for the tool's role, but conciseness and structure are good.

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 has one fully described parameter, annotations covering safety and idempotency, and an output schema, so the description does not need to explain returns. However, for a movie-state configuration tool, it omits whether prior sequences are overwritten and how states are referenced, leaving some operational gaps.

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%, and the schema itself explains the specification string with concrete examples ("1 x30" and "1 -30"). The description adds no parameter meaning beyond that, so the baseline 3 is appropriate.

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

Purpose4/5

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

The description states a specific verb (defines) and resource (a sequence of states for movie playback), which is clear and actionable. It does not explicitly differentiate itself from siblings like mplay, mstop, frame, or morph_states, so it stops short of a 5.

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 explicit when-to-use guidance, no exclusions, and no mention of alternatives such as mplay, mstop, frame, or morph_states. The movie-playback context implies usage, but an agent must infer it entirely.

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