Skip to main content
Glama
kali-mcp-server

kali-mcp-server

by rangta10

set_info

Retrieve Social Engineering Toolkit details on attack vectors, modules, payloads, or help options to assess social engineering attack capabilities.

Instructions

Get information about Social Engineering Toolkit capabilities and attack vectors

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

Input Schema

NameRequiredDescriptionDefault
info_typeNoType of info: 'vectors', 'modules', 'payloads', 'help'vectors

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. The word "Get" implies a non-destructive read, which is weak but real signal; however, there is nothing about whether the tool runs locally, requires SET to be installed, returns static documentation, or has any side effects. For an unannotated tool this is a thin disclosure.

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?

A single front-loaded sentence with no wasted words. It is efficiently sized for a one-parameter info tool, though that brevity is also the source of its missing guidance.

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

Completeness3/5

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

For a simple one-parameter reference tool with no output schema and no annotations, the description is minimally adequate: it names the domain of information available. It is incomplete in that it never explains what the four info_type modes actually return, which is the main thing an agent needs to choose a value.

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 coverage is 100%, and the schema itself enumerates the accepted values ('vectors', 'modules', 'payloads', 'help') with a default, so the parameter is already well documented. The description adds no meaning beyond that and does not even mention the info_type selector, which is the correct baseline 3 given the schema does the heavy lifting.

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?

States a specific verb ("Get information") and a specific resource ("Social Engineering Toolkit capabilities and attack vectors"), so an agent can tell this is a read-only reference lookup rather than an execution tool. It stops short of distinguishing itself from sibling info-style tools such as metasploit_exploit_info, so it is clear but not differentiated.

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?

There is no explicit when-to-use, when-not-to-use, or alternative guidance. The agent can only infer from the phrasing that this is for learning about SET capabilities, with nothing about prerequisites (e.g., SET being installed) or how it relates to the many offensive siblings.

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