Skip to main content
Glama

system_inspect_port

Inspect a local TCP port to identify the listening process by PID and name, helping diagnose port conflicts and find the owning application.

Instructions

Inspecte quel processus (PID et nom) écoute sur un port TCP local donné

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_inspect_port"
  }
}

Input Schema

NameRequiredDescriptionDefault
portYesNuméro du port TCP à inspecter (ex: 3000, 5000, 8080)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does not state what happens when no process listens on the port (error, empty result, or null), whether elevated privileges or platform-specific tools are needed, or whether the port must be in LISTEN state. Only the read-only nature is weakly implied by 'Inspecte'.

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 front-loaded sentence with zero filler; the outcome (PID and name) is stated up front and nothing is repeated from the schema.

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 one-parameter read-only tool with full schema coverage and no output schema, the definition is close to sufficient and even hints at the return content (PID and name). It is still missing the no-listener edge case and any permission or platform caveats, which matter for a system-inspection tool.

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 description coverage is 100% and the single parameter documents range and examples, so the baseline is 3. The description adds only the 'local TCP' qualifier, which is consistent with but not richer than the schema.

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 names a specific verb ('Inspecte') and resource ('quel processus (PID et nom) écoute sur un port TCP local'), so an agent knows exactly what it returns: the PID and name of the listening process. It does not differentiate itself from the sibling system_free_port, but the purpose itself is unambiguous.

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 explicit guidance on when to use this tool versus alternatives such as system_free_port, nor any stated prerequisites or exclusions. The word 'Inspecte' implies a diagnostic use case, but the agent must infer that on its own.

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