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

artifact_register

Register a file as an artifact by specifying its source path. Optionally assign a name and choose to move rather than copy.

Instructions

Kali Agent MCP tool: artifact_register

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>"
    },
    "name": "artifact_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
moveNo
nameNo
sourceYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.0

TDQS

D1.1/5.0
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It does not mention side effects, required permissions, or whether the operation is destructive. The word 'register' implies a write action, but no confirmation is given.

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

Conciseness2/5

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

The description is extremely short, but it is not concise in a helpful way—it omits essential information. Under-specification cannot be equated with conciseness.

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 the tool's 3 parameters, no schema descriptions, and the existence of related artifact tools, the description is completely inadequate. It fails to provide enough context for appropriate use.

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?

Schema coverage is 0%, and the description adds no meaning to the parameters (source, move, name). Their roles remain unclear.

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 is 'Kali Agent MCP tool: artifact_register', which is tautological and gives no indication of what the tool does. It fails to specify the action (e.g., create, register an artifact from a source) and does not distinguish it from siblings like artifact_create_text.

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 is provided on when to use this tool versus alternatives. The description lacks any context or conditions for invocation.

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