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

Burp Suite for AI Agent

by whoismemas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

burp_endpoints

List unique endpoints from Burp traffic with method, path, parameters, and hit counts to reveal attack surface.

Instructions

List unique endpoints (METHOD + path) observed from Burp traffic, with query/body parameter names and hit counts. Helps identify attack surface.

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_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
methodNoFilter to a single HTTP method
url_containsNoFilter to endpoints whose URL contains this substring

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It reveals the output includes method, path, parameters, and counts, but does not disclose data freshness, caching, or session scope. Adequate but not detailed.

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: first defines functionality, second states 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 describes output fields. Does not mention pagination or limits, but for a list tool, it covers the essential information.

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%, so the description adds no new meaning beyond the parameter descriptions in the schema. Baseline score of 3 is appropriate.

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?

Clearly states it lists unique endpoints (METHOD + path) from Burp traffic with parameter names and hit counts. Distinguishes from sibling tools like burp_requests, which lists individual requests, and burp_issues, which lists vulnerabilities.

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?

Implies use for attack surface identification but lacks explicit when-to-use or when-not-to-use guidance. No alternatives mentioned despite sibling tools like burp_requests.

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