Replit MCP Server

set_active_repl

Set the active Replit workspace ID to manage files and operations for that specific project, enabling direct interaction with the selected workspace.

Instructions

Set the active repl ID for subsequent file operations

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": {
      "replId": "<replId>"
    },
    "name": "set_active_repl"
  }
}

Input Schema

Name	Required	Description	Default
`replId`	Yes	The ID of the repl to set as active

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 10, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the tool sets an active repl ID for future operations, but fails to detail critical aspects such as permission requirements, whether this change is persistent or session-based, error handling, or any side effects. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and context, making it easy to parse quickly, which is ideal for conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of setting an active state in a system with multiple repl-related tools, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral traits, error conditions, and how this tool integrates with siblings like 'list_files' or 'write_file', making it incomplete for safe and effective use.

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?

The input schema has 100% description coverage, with 'replId' clearly documented. The description adds no additional parameter semantics beyond what the schema provides, such as format examples or constraints. Given the high schema coverage, a baseline score of 3 is appropriate as the description does not compensate but also does not detract.

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 clearly states the action ('Set') and the target resource ('active repl ID'), specifying its purpose for 'subsequent file operations'. However, it does not explicitly differentiate from siblings like 'run_repl' or 'fork_repl', which might also involve repl states, leaving some ambiguity in sibling context.

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?

The description implies usage by stating it affects 'subsequent file operations', but provides no explicit guidance on when to use this tool versus alternatives like 'run_repl' or 'get_repl_details', nor any prerequisites or exclusions. This lack of comparative context limits its effectiveness in tool selection.

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