Skip to main content
Glama
Sign In
PenTest MCP

PenTest MCP

by anishxagrawal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_report

Generate a final security assessment report from a completed penetration testing session by submitting its session ID.

Instructions

Generate final security assessment report

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": {
      "session_id": "<session_id>"
    },
    "name": "get_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
session_idYesSession identifier

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so the description should disclose behavioral traits. It only states 'generate', implying a side effect, but lacks details on whether it overwrites existing reports, requires specific permissions, or returns immediately.

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?

Single sentence is very concise, front-loading the action and object. Could benefit from more context, but no unnecessary words.

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 no output schema and many sibling scanning tools, the description should explain what the report contains and any side effects. It is too sparse for a tool that presumably consolidates results.

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 one parameter 'session_id' described as 'Session identifier'. The description adds no additional meaning beyond the schema, earning the baseline score.

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?

Description 'Generate final security assessment report' clearly states it produces a report, using a specific verb and resource. It is distinct from the many scanning tools in the sibling list, but doesn't specify report format or scope.

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 on when to use this tool versus alternatives or prerequisites. The only hint is the required 'session_id', but the description does not explain how to obtain it or when the report is ready.

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