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

task_create

Create a task with a title and objective, optionally add repository, steps, and metadata to organize work within Kali Agent.

Instructions

Kali Agent MCP tool: task_create

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": {
      "title": "<title>",
      "objective": "<objective>"
    },
    "name": "task_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
repoNo
stepsNo
titleYes
metadataNo
objectiveYes

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, but it provides none. The agent learns nothing about side effects, permissions, or whether the tool is destructive or read-only.

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 lacks substance. This is under-specification, not conciseness. Every sentence should add value; here it adds none.

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?

Despite having an output schema, the description does not mention what the tool returns. It also fails to explain any nuances of the 5 parameters, leaving the agent with insufficient information for correct invocation.

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 description coverage is 0%, and the description adds no meaning to parameters like title, objective, or steps. The agent cannot infer what values are expected or how they affect the tool's behavior.

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 'Kali Agent MCP tool: task_create' is a tautology, simply restating the tool name. It does not indicate what the tool does (e.g., create a task, its scope), nor does it distinguish it from siblings like task_update or task_list.

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, its prerequisites, or alternatives. The agent has no context to decide between task_create and other similar tools.

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