Skip to main content
Glama
wallter

smart-xdebug-mcp

by wallter

get_session_status

Retrieve the current XDebug session status to check if a session is active, its state, location, and available actions. Use this to diagnose issues before starting a new session.

Instructions

Returns the current debug session status. Call this FIRST before starting a new session.

WHEN TO USE:

  • Before start_debug_session: Check if a session is already active

  • During debugging: See current location and available actions

  • After errors: Diagnose session state

RETURNS:

  • active: Whether a session exists

  • status: Current state (see below)

  • location: Current file and line when paused

  • available_actions: Valid control_execution actions

  • breakpoints: List of registered breakpoints

SESSION STATES:

  • "initializing": Starting, waiting for XDebug connection

  • "listening": Listening for connections (XDebug not connected yet)

  • "connected": XDebug connected, execution starting

  • "paused": Stopped at breakpoint - can inspect variables and step

  • "running": Code executing, waiting for breakpoint

  • "stopped": Session ended

  • "error": Session in error state

STUCK SESSION RECOVERY: If status is "initializing" for >30 seconds, the connection likely failed. Use control_execution with action="stop" to reset, then check your XDebug configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description carries full burden. It fully discloses return fields (active, status, location, available_actions, breakpoints), session states, and recovery steps. No contradictions.

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?

The description is well-structured with clear sections (WHEN TO USE, RETURNS, SESSION STATES, STUCK SESSION RECOVERY). Every sentence adds value, and it is concise without being terse.

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

Completeness5/5

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

Given the complexity of debug session status, the description is very complete. It includes all return fields, session states, and recovery instructions. No output schema exists, but the description compensates fully.

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?

The tool has 0 parameters, and schema coverage is 100%. Baseline for 0 parameters is 4. The description adds value by explaining the output, though not required for parameters.

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?

The description clearly states it returns the current debug session status and specifies it should be called first before starting a new session. It distinguishes itself from sibling tools by being a read-only status check.

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

Usage Guidelines5/5

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

The 'WHEN TO USE' section provides explicit contexts: before start_debug_session, during debugging, after errors. It also includes a 'STUCK SESSION RECOVERY' section with actionable steps, giving clear guidance on when and how to use the tool.

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/wallter/smart-xdebug-mcp'

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