Skip to main content
Glama
Sign In
MCP ZAP Server

MCP ZAP Server

by dtkmn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

zap_findings_summary

Read currently recorded alerts for a target baseUrl as a concise grouped risk summary for fast triage, even while scan work is still in progress.

Instructions

Read currently recorded alerts, including while scan work is in progress, as a concise grouped risk summary for fast triage. Alert counts do not establish scan completion, coverage, or safety. Requires a nonblank target baseUrl covered by scan evidence visible to the caller.

Input Schema

NameRequiredDescriptionDefault
baseUrlYesRequired nonblank target base URL covered by scan evidence visible to the caller, for example https://app.example.com/admin

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.14.0
    • changedInput schema / properties / baseUrl / description
      Previous value: -"Optional base URL filter to scope findings to a specific host or path, for example https://app.example.com/admin"New value: +"Required nonblank target base URL covered by scan evidence visible to the caller, for example https://app.example.com/admin"
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "baseUrl"
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that results are live/partial during running scans, that counts must not be read as completion, coverage, or safety, and that access is scoped to evidence visible to the caller. It omits read-only confirmation, pagination, and result-shape details.

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?

Three tight sentences, front-loaded with what the tool does, followed by a skeptical caveat and the precondition. No filler; every sentence changes how an agent would use the tool.

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

Completeness4/5

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

For a single-param tool with no output schema or annotations, the description covers purpose, valid timing, access scoping, and an interpretation warning. The only gap is no hint about grouping dimensions or response size.

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 description coverage is 100% and the description's wording ("nonblank target baseUrl covered by scan evidence visible to the caller") essentially restates the schema's own parameter text. Baseline 3 applies since the schema already does this work.

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 and resource ("Read currently recorded alerts") plus the output form ("concise grouped risk summary for fast triage"), which separates it in spirit from zap_findings_details. It does not name that sibling explicitly, so the differentiation is implied rather than stated.

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

Usage Guidelines4/5

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

"Including while scan work is in progress" and "for fast triage" give clear, actionable conditions for reaching for this tool over the status/detail tools. It stops short of stating an explicit exclusion or naming zap_findings_details as the alternative when full per-alert detail is wanted.

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