Skip to main content
Glama
Sign In
ForgeMCP

ForgeMCP

by hardened-steel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debugger_breakpoints

Destructive

Replaces all source-line breakpoints for a managed source file in an active debug session, enabling a precise new breakpoint set in a single call.

Instructions

Replace every source-line breakpoint for one managed source file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>",
      "source": "<source>",
      "points": "<points>"
    },
    "name": "debugger_breakpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsYes
sourceYes
timeoutNo
session_idYes

Output Schema

NameRequiredDescriptionDefault
sourceNo
snapshotYes
breakpointsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

C2.9/5.0
Behavior3/5

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

The annotations already mark this as destructive (readOnlyHint=false, destructiveHint=true). The description adds useful context by saying it replaces every existing source-line breakpoint for one file, which clarifies what gets removed. However, it does not describe session requirements, whether changes take effect immediately, or what happens when the operation fails.

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

Conciseness4/5

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

The description is a single front-loaded sentence with no wasted wording. Its terseness is appropriate structurally, though it leaves important semantic gaps.

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

Completeness2/5

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

This is a destructive breakpoint-replacement operation with four parameters and no output-schema explanation needed. The one-sentence description is not complete enough for an agent to confidently invoke it, because it omits parameter meanings, session prerequisites, and the relationship to the other breakpoint tools.

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

Parameters2/5

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

Schema description coverage is 0% for the top-level parameters, so the description must compensate. It vaguely implies a source file and a set of breakpoints, but it never explains session_id, the source string, the points array structure, or the optional timeout.

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

Purpose4/5

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

The description states a specific verb ("Replace") and resource ("every source-line breakpoint for one managed source file"). The qualifier "source-line" helps distinguish it from function or exception breakpoint tools, though no sibling is explicitly named.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus debugger_function_breakpoints or debugger_exception_breakpoints. It also does not mention that an empty points array may clear all breakpoints, or what session state is required.

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

Deploy Server

Other Tools