Skip to main content
Glama
Sign In
Burp Suite for AI Agent

Burp Suite for AI Agent

by whoismemas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

burp_issues

Retrieve security findings queued for import into Burp Scanner. Lists confirmed issues ready to be added to your Burp project.

Instructions

List security findings/issues queued for Burp import. These are confirmed findings that can be imported as Burp Scanner issues.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It indicates a read-only operation ('List') and adds context that findings are 'confirmed' and 'can be imported.' Could mention absence of side effects or what happens if queue empty, but is adequate for a simple list tool.

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 sentences, front-loaded with purpose, no unnecessary words.

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?

No output schema, but description sufficiently explains what is listed and the context (queued for Burp import, confirmed). Could mention that output is an array, but given low complexity, it is complete enough.

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

Parameters4/5

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

No parameters in schema (100% coverage), so baseline is 4. Description does not need to add param info; it adds no harmful information.

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 it lists security findings/issues queued for Burp import, using specific verb ('List') and resource ('security findings/issues queued'). It distinguishes from siblings like 'burp_requests' (raw requests) and 'burp_import_issue' (import action).

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?

The description implies usage context (queued for import) but does not explicitly state when to use vs. alternatives or when not to use. No direct comparisons to siblings.

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