Rosetta MCP Server

Overview Schema Source Related Servers Discussions Admin

install_pyrosetta_installer

Install PyRosetta with the pyrosetta-installer package when it is not available for scoring or design tasks. Requires local installation and takes 10-30 minutes.

Instructions

Install PyRosetta using the pyrosetta-installer package. Takes 10-30 minutes. Use when PyRosetta is not available and needed for scoring or design. Requires local installation.

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

Input Schema

Name	Required	Description	Default
`silent`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.3.1May 29, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Discloses time to install (10-30 minutes) and prerequisite of local installation. Annotations provide no destructive hint; description does not add detail on potential system changes or network usage.

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?

Three concise sentences, front-loading purpose and usage. No wasted words.

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?

Adequate for a simple install tool, but missing parameter documentation leaves a gap. Output schema not needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'silent' has no description in schema (0% coverage) and is not mentioned in the tool description. Agent cannot infer its effect.

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?

Description clearly states 'Install PyRosetta' with specific method and context. No sibling tool performs installation, so it is well-differentiated.

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?

Explicitly states when to use: when PyRosetta is not available and needed for scoring or design. Mentions requirement of local installation. No alternatives listed, but none exist among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.