Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_process_snapshot

Read-onlyIdempotent

Capture a container’s process table and active network connections for runtime inspection, with an option to include or omit connection data.

Instructions

Return the container process table and active network connections.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "oc_process_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_connectionsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no repetition. The description adds the useful behavioral detail that only "active" connections are returned rather than a full connection history, but says nothing about snapshot freshness, pagination or truncation limits.

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?

One sentence, front-loaded with the primary resource and no filler. Nothing is restated unnecessarily.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple, has one optional boolean, and ships an output schema, so return values need no prose explanation. The only real gap is what the connections toggle suppresses when disabled, which is minor for a read-only diagnostic 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?

With a single parameter at 0% schema description coverage, the description must carry meaning, and it partially does: mentioning "active network connections" implies the include_connections flag governs that portion of the output. It never names the parameter, states the default, or explains what false yields.

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?

Uses a specific verb ("Return") with two concrete resources: the container process table and active network connections. That clearly distinguishes it from a browser-only snapshot such as oc_browser_snapshot, though the description never names or differentiates against sibling tools explicitly.

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 word "container" scopes it to container-internal state rather than host or browser state, which implicitly guides usage. However, there is no explicit when-to-use, when-not-to-use, or pointer to any alternative tool for network or process inspection.

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