Skip to main content
Glama

pwndbg_set_breakpoint_advanced

Set breakpoints precisely using function name, address, module offset, or file:line. Configure conditions, auto-continue, naming, and one-shot behavior.

Instructions

Set a breakpoint with full control over address, module, auto-continue, and naming.

Supports all common breakpoint styles:

  • By function name: name="CreateXmlReader"

  • By address: address="0x10027cacc"

  • By module+offset: module="Xmllite", offset="0x3cf8"

  • By file+line: address="file.c:42"

Args: session_id: The UUID of the session. address: Address or file:line expression. Mutually exclusive with name. name: Symbol name to break on. Mutually exclusive with address. module: Restrict breakpoint to this module (e.g., "Xmllite"). offset: Module-relative offset (hex string). Requires module to be set. auto_continue: If True, breakpoint auto-continues (counts hits without stopping). bp_name: Assign a human-readable name to the breakpoint for later reference. condition: Optional condition expression (breakpoint only fires if true). one_shot: If True, breakpoint is deleted after first hit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
session_idYes
addressNo
nameNo
moduleNo
offsetNo
auto_continueNo
bp_nameNo
conditionNo
one_shotNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It describes the action 'set a breakpoint' with options, but lacks details on persistence, side effects, or lifecycle of the breakpoint.

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 concise and well-structured: a brief intro, bullet-point examples, then a parameter list. Every sentence adds value without redundancy.

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 complexity (9 parameters, no annotations), the description covers all parameters and their relationships. It lacks mention of return values or error conditions, but an output schema exists to cover return format.

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

Parameters5/5

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

Schema description coverage is 0%, so the tool description fully explains all 9 parameters, including mutual exclusivity of address/name, dependency of offset on module, and examples. This adds essential meaning beyond the schema.

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 the tool's purpose: 'Set a breakpoint with full control' and lists multiple breakpoint styles. It distinguishes itself from simpler breakpoint tools like pwndbg_set_breakpoint.

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?

The description provides examples of breakpoint styles but does not explicitly state when to use this advanced version versus alternatives like pwndbg_set_breakpoint. Usage context is implied but not clarified.

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/Micro-Evaluation-Group/pwndbg-lldb-mcp'

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