Skip to main content
Glama

debugger_set_breakpoint_at_function

Set a breakpoint on any function expression, such as app.saveOrder, without knowing its file. Pause at the first statement, with optional condition for targeted debugging.

Instructions

Set a breakpoint on a function you can name, without knowing which file it lives in. Give any expression that evaluates to a function — 'app.saveOrder', 'MyClass.prototype.load', a framework helper — and DevCDP finds its definition and breaks at its first statement. Use this when you know what runs but not where it is defined; use debugger_set_breakpoint when you already have a file and line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conditionNoJavaScript condition — pause only when it is truthy, e.g. 'id === 42'.
auto_resumeNoDefault true: capture scope/console/network on hit, then resume, so the page is never left frozen and the action that tripped it completes. Pass false to hold the pause for stepping; released after maxPauseMs regardless.
function_expressionYesJavaScript evaluating to the function itself — no call parentheses. For example 'app.store.save', not 'app.store.save()'.
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It clearly explains that DevCDP resolves any function expression to its definition and breaks at its first statement. It does not cover breakpoint persistence or the return result, but the core runtime behavior is transparent enough for selection and invocation.

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?

Two sentences with no filler. The main behavior is front-loaded, examples are compactly integrated, and the sibling comparison appears at the end without bloating the description.

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?

For a 3-parameter tool with no output schema and no annotations, the description covers purpose, usage, and behavior well. It slightly lacks return-value expectations and breakpoint lifecycle details, but those are not critical for selecting and invoking this tool.

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

Parameters3/5

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

Schema coverage is 100%, so the baseline is 3. The description adds helpful examples like 'app.saveOrder' and 'MyClass.prototype.load', reinforcing the function_expression parameter, but the schema already documents the key semantics such as 'no call parentheses'. No additional parameter meaning is needed.

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 states a specific action: set a breakpoint on a named function without knowing its file. It also distinguishes itself from the sibling debugger_set_breakpoint by contrasting function-based vs file-and-line-based breakpoints, so an agent can select the right tool immediately.

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?

It gives an explicit when-to-use rule: 'Use this when you know what runs but not where it is defined; use debugger_set_breakpoint when you already have a file and line.' This is direct, actionable guidance that names the alternative and the selecting condition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/Dayananda-D/Devcdp'

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