Skip to main content
Glama
Sign In
MCP-Connect — Kali Agent MCP v2

MCP-Connect — Kali Agent MCP v2

by asarlashmit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

copy_path

Copies files or directories from source to destination, with an option to overwrite existing files.

Instructions

Kali Agent MCP tool: copy_path

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": {
      "source": "<source>",
      "destination": "<destination>"
    },
    "name": "copy_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
sourceYes
overwriteNo
destinationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

D1/5.0
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as whether the operation is destructive, permissions required, or side effects. It carries the full burden but adds nothing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single phrase that repeats the tool name. It is under-specified rather than concise; every sentence should add value, but none does.

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

Completeness1/5

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

Given sibling tools like move_path and delete_path, the description should clarify that copy duplicates a file or path. It also fails to mention the return value despite an output schema existing. The description is incomplete for the tool's complexity.

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

Parameters1/5

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

The input schema has three parameters (source, destination, overwrite) with no descriptions, and the description adds no meaning about their purpose or usage. With 0% schema description coverage, the description fails to compensate.

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

Purpose1/5

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

The description simply restates the tool name without providing a verb or resource. It says 'Kali Agent MCP tool: copy_path', which is a tautology and gives no indication of what the tool does.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives like move_path, delete_path, or write_file. The description provides no context for selection.

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