Skip to main content
Glama

debugpy_logs

Retrieve logs from Docker containers to analyze Python process behavior and generate breakpoint plans for debugging with debugpy.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
containerYes
tailNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for the 'debugpy_logs' tool. Decorated with @mcp.tool(), it runs 'docker logs --tail' on the specified container, combines stdout and stderr, and returns a LogsResult with the combined logs.
    @mcp.tool()
    def debugpy_logs(container: str, tail: int = 250) -> dict[str, Any]:
        proc = run(["docker", "logs", "--tail", str(tail), container], timeout=30, check=False)
        combined = ""
        if proc.stdout:
            combined += proc.stdout
        if proc.stderr:
            if combined:
                combined += "\n"
            combined += proc.stderr
        return LogsResult(ok=proc.returncode == 0, container=container, tail=tail, logs=combined.strip()).model_dump()
  • Pydantic model defining the output schema for debugpy_logs. Contains fields: ok (bool), container (str), tail (int), and logs (str).
    class LogsResult(BaseModel):
        ok: bool
        container: str
        tail: int
        logs: str
  • The @mcp.tool() decorator registers the debugpy_logs function as an MCP tool with the FastMCP server instance.
    @mcp.tool()
  • Helper function 'run' that executes subprocess commands with configurable timeout and error checking. Used by debugpy_logs to invoke 'docker logs'.
    def run(cmd: list[str], *, timeout: int = DEFAULT_TIMEOUT, check: bool = True) -> subprocess.CompletedProcess[str]:
        proc = subprocess.run(cmd, capture_output=True, text=True, timeout=timeout)
        if check and proc.returncode != 0:
            raise ToolError(
                f"Command failed ({proc.returncode}): {' '.join(cmd)}\n"
                f"STDOUT:\n{proc.stdout}\nSTDERR:\n{proc.stderr}"
            )
        return proc
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