Skip to main content
Glama
Sign In
LocalREPL MCP Server

LocalREPL MCP Server

by angrysky56
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_repl

Delete a specific REPL instance by providing its ID to free resources and manage active sessions.

Instructions

Delete a REPL instance.

Args:
    repl_id: ID of the REPL to delete

Returns:
    str: Confirmation message

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": {
      "repl_id": "<repl_id>"
    },
    "name": "delete_repl"
  }
}

Input Schema

NameRequiredDescriptionDefault
repl_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, and the description only states the action without disclosing behavioral traits such as irreversibility, permissions required, or impact on associated processes. This is insufficient for a destructive tool.

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 extremely concise with three lines for the main purpose, followed by Args and Returns. Every sentence is necessary and front-loaded.

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?

Considering the tool's simplicity (one parameter, no output schema, no annotations), the description is adequate but lacks details on return value format or error handling. Could be more thorough.

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 description adds meaning beyond the schema by stating 'ID of the REPL to delete' for the repl_id parameter. Given 0% schema description coverage, this compensation is adequate but minimal.

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?

The description clearly states 'Delete a REPL instance,' providing a specific verb and resource. It distinguishes from sibling tools like 'kill_shell' or 'spawn_shell' by focusing on REPL deletion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when a REPL needs to be removed, but it offers no explicit guidance on when to use this tool over alternatives like 'kill_shell' or prerequisites. No exclusions or alternative tool mentions.

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