Skip to main content
Glama
Sign In
chungus-kali-mcp

chungus-kali-mcp

by cryptopepy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

ctf_connect

Connect to a CTF platform via URL, optionally authenticating with cookies or API token to access challenges.

Instructions

Connect to CTF platform.

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": {
      "url": "<url>"
    },
    "name": "ctf_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
cookiesNo
platformNoctfd
api_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

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 carries the full burden of behavioral disclosure. It only states 'Connect to CTF platform' without explaining side effects (e.g., persistent session), authentication requirements, or failure modes. This is a significant gap for a tool that likely manages state.

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

Conciseness3/5

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

The description is a single concise sentence, which is appropriately front-loaded and not verbose. However, it is under-specified—too short to convey the tool's purpose beyond a restatement of the name. It earns a middle score because it is not bloated, but it lacks substance.

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 the tool has 4 parameters, no annotations, and no output schema, the description fails to provide essential context about when to use it, what it returns, or how it behaves. It is minimally viable for an agent to guess, but not sufficient for reliable invocation in a complex environment with many sibling tools.

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

Parameters2/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, but it doesn't mention any of the four parameters (url, cookies, platform, api_token). The parameter names are somewhat self-explanatory, but the description adds no meaning about required vs. optional, defaults, or how they relate to connecting.

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

Purpose4/5

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

The description uses a specific verb+resource pattern: 'Connect to CTF platform.' It clearly distinguishes this tool from sibling ctf_status (which checks connection status) by implying an establishment action, though it could be more explicit about what 'connect' entails.

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

Usage Guidelines2/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 like ctf_status or ctf_list_challenges. It does not mention prerequisites (e.g., need for a URL or credentials) or when this should be called before other operations.

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