Skip to main content
Glama
FuzzingLabs

SecPipe

Official
by FuzzingLabs
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

generate_report

Aggregate execution history, tool outputs, and artifacts into a structured report, save it to .secpipe/reports/, and return the content immediately.

Instructions

Generate a comprehensive analysis report for the current project.

Aggregates all execution history, tool outputs, and tracked artifacts into a structured report. The report is saved to .secpipe/reports/ and its content is returned so the agent can read it immediately.

:param title: Optional report title. Defaults to the project folder name. :param report_format: Output format — "markdown" (default) or "json". :param output_path: Optional absolute path to save the report. When omitted, the report is saved automatically to .secpipe/reports/. :return: Report content, save path, and counts of included items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
report_formatNomarkdown
output_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses aggregation of execution history, tool outputs, and artifacts, save location, and immediate return. Could mention if overwriting occurs.

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

Conciseness5/5

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

Two concise paragraphs with front-loaded purpose and clear parameter docs. No superfluous information.

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

Completeness5/5

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

Given the presence of an output schema, the description covers behavior, parameters, and return value well. It is complete for a report generation tool.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description provides docstring-style explanations for each parameter, adding significant meaning about optionality, defaults, and format options.

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

Purpose5/5

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

The description clearly states 'Generate a comprehensive analysis report for the current project', specifying the verb and resource. It distinguishes from sibling tools like list_reports which list existing reports.

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

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied through context and sibling tool list, but the description does not explicitly state when to use this tool vs alternatives like list_reports.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/FuzzingLabs/secpipe'

If you have feedback or need assistance with the MCP directory API, please join our Discord server