Skip to main content
Glama
Sign In
LocalREPL MCP Server

LocalREPL MCP Server

by angrysky56
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

wait_shell

Block until a spawned process exits or times out, then return exit info.

Instructions

Block until a spawned process exits (or timeout). Returns exit info.

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": {
      "proc_id": "<proc_id>"
    },
    "name": "wait_shell"
  }
}

Input Schema

NameRequiredDescriptionDefault
proc_idYes
timeout_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses blocking behavior and timeout, but does not mention side effects, error handling on timeout, or whether the tool is destructive. Basic transparency but lacks detail.

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?

A single sentence with no redundancies. Every word is necessary and the sentence is front-loaded.

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 no output schema and no parameter descriptions, the description is incomplete. It does not specify what 'exit info' includes, how to obtain 'proc_id', or behavior on timeout. Context from sibling tools is not leveraged.

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?

Schema description coverage is 0%, so the description must explain parameters. It does not describe 'proc_id' or 'timeout_seconds', leaving the agent to infer meaning from names alone.

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 it blocks until a spawned process exits or times out, returning exit info. The verb 'block' and resource 'spawned process' are specific, but it does not differentiate from sibling tools like 'reap_exited' that also handle exits.

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?

No explicit guidance on when to use this tool versus alternatives like 'spawn_shell' or 'reap_exited'. Usage is only implied from the description.

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