Skip to main content
Glama
Sign In
LocalForge

LocalForge

by tanskong
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

process_stop

DestructiveIdempotent

Stop a running LocalForge background child process. Provide the process ID to terminate it.

Instructions

Stop a LocalForge background child process.

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": {
      "process_id": "<process_id>"
    },
    "name": "process_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
process_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds scope value by noting it targets 'LocalForge background child process', implying it won't touch arbitrary PIDs, but it says nothing about whether the stop is graceful or forced, or what happens on an invalid/already-dead id.

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?

One short, front-loaded sentence with zero filler. It is efficient, though the brevity edges into under-specification given the surrounding gaps.

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?

An output schema exists, so return values needn't be described, and annotations cover the mutation profile. Still missing is how to obtain a valid process_id and how this pairs with process_status, which an agent needs to invoke the tool correctly in sequence.

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

Parameters2/5

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

Schema description coverage is 0% and the single parameter process_id carries no description in the schema. The description does not explain where process_id comes from (e.g., process_status or a launch call) or its expected format, so the only required argument is effectively undocumented.

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?

States a specific verb (Stop) and resource (LocalForge background child process), which is unambiguous about the action. However, it never differentiates itself from the sibling process_status tool or clarifies the relationship between the two, so an agent must infer the division of labor.

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 guidance on when to stop a process versus checking it first with process_status, nor any prerequisite such as how a process is started or when stopping is appropriate. Usage is only weakly implied by the tool name.

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