MCP-Connect — Kali Agent MCP v2

Overview Schema Source Related Servers Discussions Admin

git_clean_preview

Preview untracked files and directories that Git would remove, including optionally ignored files, for a specified path.

Instructions

Kali Agent MCP tool: git_clean_preview Explicit execution timing is supported. Before calling, deliberately choose expected_runtime_seconds, timeout_seconds, check_after_seconds, poll_interval_seconds, and on_timeout. Use on_timeout='continue_background' for long work that should return a durable job_id for later job_status/job_logs/job_wait checks; use 'kill' or 'return_partial' for bounded synchronous work.

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

Input Schema

Name	Required	Default
`path`	No	.
`ignored`	No
`on_timeout`	No	return_partial
`directories`	No
`timeout_seconds`	No
`check_after_seconds`	No
`poll_interval_seconds`	No
`expected_runtime_seconds`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jul 10, 2026

TDQS

C2.6/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It mentions explicit execution timing and background job capability, but omits whether the tool is destructive, what it actually does (preview of clean), and any permissions or side effects. The core behavior is missing.

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?

The description is relatively concise at three sentences, with key advice front-loaded. However, the first sentence is redundant ('Kali Agent MCP tool: git_clean_preview') and could be removed without loss. Overall efficient but not maximally lean.

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

Completeness2/5

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

Given 8 parameters, no schema descriptions, many sibling tools, and an output schema (unreferenced), the description is incomplete. It fails to explain the tool's primary action, output, or critical parameters like path. The focus on timing overshadows essential context.

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 0%, so the description must compensate. It explains timing parameters (expected_runtime_seconds, timeout_seconds, check_after_seconds, poll_interval_seconds) and on_timeout values. However, it ignores path, ignored, and directories, which are critical to the tool's action. Partial coverage improves over nothing.

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

Purpose2/5

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

The description does not state what the tool does. It only says 'Kali Agent MCP tool: git_clean_preview' and then discusses execution timing. It fails to indicate that this tool previews a git clean operation, leaving the purpose ambiguous. Compared to sibling tools like git_status or git_diff, it lacks differentiation.

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 description provides guidance on when to use different on_timeout values (continue_background vs kill/return_partial), implying usage context for long vs bounded work. However, it does not specify when to use this tool instead of other git tools or how it fits into a workflow.

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

Deploy Server