iStoreOS MCP Server

Overview Schema Source Related Servers Discussions Admin

get_active_connections

Monitor active network connections from the conntrack table, displaying protocol, src, dst, ports, and state. Use the limit parameter to cap results (default 500).

Instructions

Get active network connections from conntrack table (protocol, src, dst, ports, state). Use 'limit' to cap results (default 500)

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": "get_active_connections"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 13, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It implies a read operation and lists the returned fields, but it does not disclose any potential side effects, authentication requirements, rate limits, or behavior when the limit is exceeded. The minimal information is adequate for a simple retrieval tool.

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?

The description is extremely concise with two sentences. The first sentence states the action and output fields, and the second covers parameter usage. No unnecessary words.

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?

For a simple retrieval tool with one optional parameter, the description covers the key points: what data is returned and how to control the limit. An output schema likely provides the full return structure, so the description is sufficiently complete.

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

Parameters4/5

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

The description adds meaning to the 'limit' parameter by stating it 'caps results' and notes the default value, which goes beyond the schema's type and default. Despite 0% schema description coverage, this explanation compensates well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves active network connections from the conntrack table and lists the fields returned (protocol, src, dst, ports, state). It is distinct from sibling tools, which focus on specific statuses or system info.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains that the 'limit' parameter caps results (default 500), providing usage guidance. It does not explicitly state when to use this tool versus alternatives, but given the sibling tool names, the context is clear.

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