Skip to main content
Glama
titaniumtushar

burp-mcp-plus

js_list

List all registered JavaScript sources to identify and inspect client-side scripts for enhanced web application security analysis.

Instructions

List all registered JS sources.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • Actual implementation of list_sources() — iterates _REGISTRY and returns a list of dicts with name, manifest, files count, and missing_on_disk count.
    def list_sources() -> list[dict[str, object]]:
        return [
            {
                "name": s.name,
                "manifest": s.manifest_path,
                "files": len(s.records),
                "missing_on_disk": sum(1 for r in s.records if not r.abs_path),
            }
            for s in _REGISTRY.values()
        ]
  • The js_list MCP tool handler — decorated with @mcp.tool(), calls jsfiles.list_sources() and returns JSON.
    @mcp.tool()
    def js_list() -> str:
        """List all registered JS sources."""
        return json.dumps(jsfiles.list_sources(), indent=2)
  • Registration of js_list as an MCP tool via @mcp.tool() decorator on the function.
    @mcp.tool()
    def js_list() -> str:
  • The _REGISTRY dict that stores JsSource objects, used by list_sources().
        _REGISTRY[name] = src
        return src
    
    
    def get(name: str) -> JsSource:
        if name not in _REGISTRY:
            raise KeyError(f"js source {name!r} not loaded; call js_load first")
        return _REGISTRY[name]
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It only states 'List all registered JS sources' without mentioning side effects, permissions, or whether it is read-only. The description lacks crucial behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, straightforward sentence with no unnecessary words. It is concise but could benefit from additional structure or context.

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?

Given the tool's simplicity (0 parameters, existing output schema), the description is largely adequate. It explains the core functionality, and the output schema can provide return value details. However, it could be more complete by noting that the list includes all sources without filtering.

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?

There are no parameters, so schema description coverage is trivially 100%. The description adds no parameter-specific information, but none is needed. A baseline of 3 is appropriate, raised slightly due to the absence of required elaboration.

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?

The description clearly states the action 'List' and the resource 'registered JS sources'. It is specific and distinguishes from siblings like 'js_search' or 'js_files', though it does not explicitly differentiate.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'js_search' for filtering. There are no use case examples or exclusions.

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