Skip to main content
Glama
Sign In
PenTest MCP

PenTest MCP

by anishxagrawal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

init_session

Begin a new security assessment by supplying a target URL or domain, setting up a session for penetration testing.

Instructions

Initialize new security assessment session

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": {
      "target": "<target>"
    },
    "name": "init_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesTarget URL or domain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description bears full responsibility for disclosing behavior, but it only states the initialization action. It does not explain what a 'session' entails, whether it is safe, what side effects occur, or if authentication is needed. This lack of detail leaves the agent uncertain about the tool's impact.

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 very short (one line) and front-loaded, but it under-specifies the tool's role. While brevity is valued, the content does not fully earn its place due to missing critical context.

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 simplicity of the tool (one parameter, no output schema), the description should provide more context about what initializing a session accomplishes, such as whether it creates a persistent state or requires prior steps. The lack of this information makes the definition incomplete for reliable agent use.

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% with 'target' described as 'Target URL or domain', which is sufficient. The description adds no extra parameter insight, so it meets the baseline but does not exceed it.

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 clearly states the action ('initialize') and the resource ('new security assessment session'), making the tool's primary function understandable. However, it does not differentiate from sibling tools like 'quick_scan' or 'extensive_scan', which may also be session-related.

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. There is no mention of prerequisites, context, or conditions that would help an agent decide to invoke init_session over other 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