Skip to main content
Glama
Sign In
Free Codin Agent

Free Codin Agent

by office233
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

vscode_add_breakpoint

Destructive

Adds a conditional or unconditional breakpoint at a specific file and line in VS Code to pause code execution for debugging.

Instructions

Add a breakpoint (optionally conditional).

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": {
      "file": "<file>",
      "line": "<line>"
    },
    "name": "vscode_add_breakpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileYesAbsolute file path
lineYes1-based line
conditionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true and non-idempotent, but the description adds nothing: it doesn't say whether breakpoints persist across sessions, whether re-adding the same line is harmless, or that a debug session must be running. With annotations present the bar is lower, yet the description contributes no behavioral context at all.

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?

A single compact sentence with no filler and the optional aspect front-loaded. It is efficient, though borderline under-specified rather than maximally informative.

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 state-mutating debug tool with no output schema, the description omits the debug-session prerequisite, where the breakpoint attaches, and any indication of success/failure. An agent could not confidently invoke this without inferring context from outside the definition.

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 67%: 'file' and 'line' are documented in the schema, while 'condition' has no schema description. The description's 'optionally conditional' partially compensates by telling the agent what the parameter is for, but it gives no expression syntax or scope for the condition.

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?

States a specific verb and resource ('Add a breakpoint') plus a scope modifier ('optionally conditional'). No sibling performs this action, so differentiation is unnecessary, but the description stops short of saying where the breakpoint lands or its lifecycle.

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?

No when-to-use guidance, no prerequisites. Critically, it never states that an active debug session is required, or how this relates to vscode_debug_state — the one sibling an agent would plausibly pair with it.

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