Skip to main content
Glama
titaniumtushar

burp-mcp-plus

dedup_get

Retrieve a deduplicated HTTP request and response by index from Burp Suite dedup storage, returning metadata and previews or full raw data.

Instructions

Fetch a dedup entry by its 1-based index.

By default returns metadata + truncated request/response previews. Set full=True to get the complete raw request and response.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
indexYes
fullNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool function 'dedup_get' - fetches a dedup entry by its 1-based index. Returns metadata plus truncated request/response previews by default, or full raw request/response when full=True.
    @mcp.tool()
    def dedup_get(name: str, index: int, full: bool = False) -> str:
        """Fetch a dedup entry by its 1-based index.
    
        By default returns metadata + truncated request/response previews. Set
        `full=True` to get the complete raw request and response.
        """
        src = dedup.get(name)
        target = next((e for e in src.entries if e.index == index), None)
        if target is None:
            raise KeyError(f"no entry index={index} in source {name!r}")
        out: dict[str, Any] = {
            "index": target.index,
            "method": target.method,
            "url": target.url,
            "status": target.status,
            "length": target.length,
            "parameters": target.parameters,
        }
        if full:
            out["request"] = target.request
            out["response"] = target.response
        else:
            out["request_preview"] = target.request[:1024]
            out["response_preview"] = target.response[:1024]
            out["request_bytes"] = len(target.request)
            out["response_bytes"] = len(target.response)
        return json.dumps(out, indent=2)
  • Registration of dedup_get as an MCP tool via @mcp.tool() decorator on line 672.
    @mcp.tool()
  • Helper function 'dedup.get()' called by dedup_get to retrieve a registered DedupSource by name from the in-process registry.
    def get(name: str) -> DedupSource:
        if name not in _REGISTRY:
            raise KeyError(f"dedup source {name!r} not loaded; call dedup_load first")
        return _REGISTRY[name]
  • The DedupSource dataclass returned by dedup.get(), containing the list of DedupEntry instances.
    @dataclass
    class DedupSource:
        name: str
        path: str
        entries: list[DedupEntry]
  • The DedupEntry dataclass representing a single dedup entry, with fields accessed by dedup_get.
    @dataclass
    class DedupEntry:
        index: int  # 1-based as in the file
        method: str
        url: str
        status: int | None
        length: int | None
        parameters: str
        request: str
        response: str
Behavior4/5

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

With no annotations, the description carries full burden. It clearly states that by default it returns metadata plus truncated previews, and setting full=True gives complete raw data. This provides a solid behavioral contract, though it avoids discussing error behavior or index bounds.

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-sentence description: first sentence states purpose, second explains default behavior and option. No extraneous text, efficient and front-loaded.

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?

Has output schema, so return values do not need detailed explanation. Description covers default vs full modes adequately. Could mention that entries are from a dedup store or index validity, but overall complete for its complexity.

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 0%. Description clarifies that index is 1-based and full is a boolean for full vs truncated output. However, the 'name' parameter is not explained, leaving its purpose ambiguous. The description adds value but not complete coverage.

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?

Description clearly states 'Fetch a dedup entry by its 1-based index', identifying the action and resource. It distinguishes from siblings like dedup_list (lists all) and dedup_search (searches) by specifying indexed retrieval.

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?

No explicit guidance on when to use this tool versus alternatives like dedup_list or dedup_search. The context of '1-based index' implies usage when the index is known, but no when-not-to or alternative references are provided.

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/titaniumtushar/burp-mcp-plus'

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