This MCP server has severe definition quality issues. Only 3 tools are exposed, all with minimal descriptions and no structured output schemas. Tool names lack action verbs (e.g., 'Show proxy history' instead of 'get_proxy_history'). Parameters exist but lack descriptions. No error handling guidance, no pagination support, and no documented return types. The server appears to be a wrapper around Burp Suite with hardcoded tool logic, but definitions do not meet production standards for agentic tool composition.
Tools (3)
Base64 encoderead only43/100
Encodes text to Base64 format
Generate random stringread only22/100
Generates a random string
Show proxy historyread only20/100
Displays the proxy request/response history from Burp Suite
Tool names do not start with action verbs. 'Show proxy history' should be 'get_proxy_history'; 'Generate random string' should be 'generate_random_string'. LLMs rely on verb_noun naming to infer intent from the name alone.
No output schemas documented. Tools return data but LLMs cannot know what fields to expect. 'Show proxy history' should document: does it return an array? What fields does each entry contain (request, response, timestamp, status)? Without this, downstream chaining is impossible.
Parameter descriptions are missing or trivial. 'Base64 encode' has input {"text": {"type": "string", "description": "Text to encode"}}, the description is too generic. Should clarify: acceptable input size? Handling of non-ASCII? What character encodings? What's returned on overflow?
Expand descriptions to 100-200 characters. Example: 'encode_base64: Encodes plaintext UTF-8 strings to RFC 4648 Base64 format. Max input 1 MB. Returns base64-encoded string. Use when preparing data for binary transport or storage.',
Document output schemas explicitly. For 'get_proxy_history': returns {type: 'array', items: {type: 'object', properties: {id: string, method: string, url: string, statusCode: number, timestamp: string (ISO 8601), requestBody?: string, responseBody?: string}}, description: 'Array of proxy records from Burp history, newest first. Limited to 100 records; use page parameter for older records.'}
Add parameter descriptions: 'Base64 encode' → text parameter should say: 'UTF-8 plaintext to encode. Max 1 MB. Non-ASCII characters are encoded as-is. Returns RFC 4648 standard Base64 (no URL-safe variant).'
Implement error handling: Document that if Burp proxy is unreachable, 'get_proxy_history' returns error 'Burp Suite proxy not available at http://127.0.0.1:9876. Ensure Burp is running with MCP extension enabled. Retry after 5s.' instead of a bare stack trace.
'Show proxy history' has zero input parameters but no documentation of what it returns. Is it paginated? How many records max? Does it filter by date, URL, method? Without clarity, LLMs cannot determine when to call it or how to interpret results.
'Generate random string' has no input parameters and no description of output format. Is it alphanumeric? How long? Is it URL-safe? Charset configurable? LLM cannot reason about when to use it.
No error handling guidance. Tools are READ_ONLY but no documentation of failure modes. What happens if 'Base64 encode' receives invalid UTF-8? What if 'Show proxy history' fails to connect to Burp? LLMs receive no recovery guidance.
Base64 encodeShow proxy historyGenerate random string
Tool descriptions are generic and under 50 characters (baseline is 194 chars avg for A+ tools). 'Encodes text to Base64 format' (33 chars) lacks context: When should LLM use this vs. a built-in encoder? Does the tool preserve line breaks? What's the max input size?
Base64 encodeShow proxy historyGenerate random string
No pagination support on 'Show proxy history'. Production tools returning lists must implement page/offset + limit parameters and document result count limits. Without pagination, large proxy history could overflow context.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) even though all tools are marked READ_ONLY at the server level. Annotations should be per-tool for clarity.
Base64 encodeShow proxy historyGenerate random string
Add idempotent annotations: all three tools are read-only and safe to retry. Add tool annotation hint to the MCP server definition: {"readOnlyHint": true} for each tool.
Document max result limits in 'get_proxy_history': 'Returns a maximum of 100 records per request. Use the page parameter to iterate through proxy history. Proxy history is retained for the current Burp session only.',
Add composition example in server README: 'To extract sensitive data from proxy history, call get_proxy_history(), filter for URLs containing 'api', then encode payloads with encode_base64() for secure display.'
Add input validation and recovery guidance: if 'encode_base64' receives a non-string, return error 'Input must be a string. If passing structured data, stringify it first with JSON.stringify().'
Consider adding a tool to list available Burp data (reports, scan results, site map) so LLM can discover what's available before calling specific tools.