Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

step_out

Exit the current function by running to completion and stopping at the caller. Use this to return from a function you stepped into, resuming debugging at the calling code.

Instructions

Step out of the current function. Blocks until the step completes.

State: STOPPED required.

Continues execution until the current function returns, then stops at the caller. Use this to exit a function you stepped into.

Escape hatch: see the dap-escape-hatch prompt for unwrapped DAP requests.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "step_out"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations provide no read/write hints. The description adds some behavioral context: blocks until complete, continues execution then stops at caller. But it does not disclose side effects or what happens to the state beyond the required STOPPED state.

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 relatively concise (5 lines) and front-loaded with the core purpose. The 'Escape hatch' line is slightly extraneous but does not significantly harm conciseness.

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?

Given the one optional parameter, no output schema, and minimal annotations, the description covers the basic operation but misses parameter explanation and potential side effects. It does not contrast with sibling tools beyond mentioning stepping into.

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

Parameters1/5

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

There is one optional parameter (thread_id) with no description in the schema. The tool description does not mention this parameter at all, leaving the agent uninformed about when or why to provide it.

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 'Step out of the current function' with a specific verb and resource. It distinguishes from siblings like step_into and step_over by explaining it exits a function you stepped into.

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

Usage Guidelines4/5

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

The description provides clear guidance: 'Use this to exit a function you stepped into' and mentions required state ('State: STOPPED required'). However, it does not explicitly state when not to use it or list alternatives.

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