Skip to main content
Glama
Sign In
ForgeMCP

ForgeMCP

by hardened-steel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

debugger_exception_breakpoints

Destructive

Select exception stop filters advertised by the current session to control which exceptions pause execution during debugging.

Instructions

Select exception stop filters advertised by the current session.

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>",
      "filters": "<filters>"
    },
    "name": "debugger_exception_breakpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
filtersYes
timeoutNo
session_idYes

Output Schema

NameRequiredDescriptionDefault
filtersYes
snapshotYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, but the description adds no behavioral context beyond them. It does not say whether calling this replaces all previously configured exception filters, whether it can be called mid-run, or what happens if a filter name is not one the session advertised.

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

Conciseness3/5

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

It is a single front-loaded sentence with no waste, but it is terse to the point of under-specification rather than being efficiently concise. There is room to add the missing when-to-use and mutation semantics without bloat.

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?

For a mutating three-parameter debugger tool with 0% schema description coverage, the description is too thin; only the output schema relieves it of explaining return values. An agent still lacks the filter naming/validation rules and the effect of the call on existing filters.

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 description coverage is 0%, so description should compensate, but it only loosely maps to 'filters' (exception stop filters) and 'session_id' ('current session'). The timeout parameter and the string-array format of filters receive no mention, leaving the schema's bare types to carry the burden.

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

Purpose3/5

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

The description names a specific resource, exception stop filters, and a verb, 'select', and the phrase 'advertised by the current session' signals the filters come from session capabilities. However, 'select' is ambiguous between reading and setting, and it does not distinguish this tool from the nearby debugger_breakpoints, debugger_function_breakpoints, or debugger_exception_info siblings.

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 when-to-use guidance: nothing says to call this before continuing/stepping, nor how it differs from debugger_breakpoints (line breakpoints) or debugger_exception_info (inspecting a thrown exception). An agent must infer the workflow entirely.

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