Skip to main content
Glama

debugpy_autodiscover_target

Automatically discover Python processes in Docker containers for debugging by analyzing service or image hints to identify target applications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
service_hintNo
image_hintNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function `autodiscover_target` that implements the autodiscovery logic. It lists running Docker containers, scores them based on service_hint and image_hint parameters, and returns the best matching container(s).
    def autodiscover_target(service_hint: str | None = None, image_hint: str | None = None) -> AutodiscoverResult:
        containers = list_containers()
        notes: list[str] = []
        scored: list[tuple[int, ContainerSummary]] = []
    
        for c in containers:
            score = 0
            haystacks = [c.name.lower(), c.image.lower(), c.ports.lower()]
            if service_hint:
                hint = service_hint.lower()
                if hint in c.name.lower():
                    score += 10
                if hint in c.image.lower():
                    score += 6
            if image_hint:
                hint = image_hint.lower()
                if hint in c.image.lower():
                    score += 10
                if hint in c.name.lower():
                    score += 3
            if "5678" in c.ports:
                score += 4
            if any(token in c.name.lower() or token in c.image.lower() for token in ["api", "fastapi", "uvicorn", "backend", "web"]):
                score += 2
            if score > 0:
                scored.append((score, c))
    
        if not scored:
            notes.append("No strong autodiscovery match found; returning all running containers.")
            return AutodiscoverResult(ok=True, candidates=containers, selected=containers[0] if containers else None, notes=notes)
    
        scored.sort(key=lambda t: (-t[0], t[1].name))
        candidates = [c for _, c in scored]
        selected = candidates[0] if candidates else None
        if selected:
            notes.append(f"Selected container '{selected.name}' as the strongest match.")
        return AutodiscoverResult(ok=True, candidates=candidates, selected=selected, notes=notes)
  • The MCP tool registration point using `@mcp.tool()` decorator. The `debugpy_autodiscover_target` function wraps the handler and converts the result to a dict via `.model_dump()`.
    @mcp.tool()
    def debugpy_autodiscover_target(service_hint: str | None = None, image_hint: str | None = None) -> dict[str, Any]:
        return autodiscover_target(service_hint=service_hint, image_hint=image_hint).model_dump()
  • Pydantic BaseModel classes `ContainerSummary` and `AutodiscoverResult` that define the input/output schema for the autodiscovery feature.
    class ContainerSummary(BaseModel):
        id: str
        name: str
        image: str
        status: str
        ports: str
    
    
    class AutodiscoverResult(BaseModel):
        ok: bool
        candidates: list[ContainerSummary] = Field(default_factory=list)
        selected: ContainerSummary | None = None
        notes: list[str] = Field(default_factory=list)
  • Helper function `list_containers` that executes `docker ps` and parses the output into ContainerSummary objects, used by the autodiscover_target handler.
    def list_containers() -> list[ContainerSummary]:
        proc = run([
            "docker", "ps", "--format", "{{.ID}}\t{{.Names}}\t{{.Image}}\t{{.Status}}\t{{.Ports}}"
        ], timeout=10)
        items: list[ContainerSummary] = []
        for line in proc.stdout.splitlines():
            parts = line.split("\t")
            if len(parts) != 5:
                continue
            items.append(ContainerSummary(id=parts[0], name=parts[1], image=parts[2], status=parts[3], ports=parts[4]))
        return items
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

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

Parameters1/5

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

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/will-garrett/debugpy-mcp'

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