Skip to main content
Glama

system_free_port

Stop the process blocking a local TCP port to free it for reuse, with a safety guard that protects vital system processes.

Instructions

Arrête proprement le processus bloquant un port TCP local (avec garde-fou de sécurité protégeant les processus système vitaux)

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": {
      "port": "<port>"
    },
    "name": "system_free_port"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYesNuméro du port TCP à libérer
forceNoSi true, force l'arrêt immédiat (/F)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It does valuable work by disclosing that this terminates a process and that a safety guard protects vital system processes, which signals destructiveness, but it is silent on permissions required, behavior when no process holds the port, whether confirmation is needed, and what the result looks like.

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 front-loaded sentence with the action and its safeguard in a parenthetical; nothing is padded or redundant. It is arguably too terse for an unannotated destructive tool, but as structure and wording go it is clean.

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?

For a destructive operation with no annotations and no output schema, the description should explain prerequisites, failure conditions, and consequences. It covers the core action and the system-process safeguard but leaves an agent without enough context to call it safely in edge cases.

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?

Schema coverage is 100%, so both 'port' and 'force' (including the /F mapping) are already documented in the schema. The description adds only the implication of graceful termination via 'proprement', which does not meaningfully extend the schema's explanation of the force flag.

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 pairs a specific verb and resource -- stopping the process that blocks a local TCP port -- so an agent immediately knows this is a termination action, not an inspection one like system_inspect_port. It stops short of naming that sibling explicitly, so differentiation is implied rather than stated.

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?

Usage is only implied: the purpose tells you it applies when a port is blocked, but there is no statement of preconditions, when to prefer inspection first, or when to choose the forced variant. No exclusions or alternative routing are given.

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