Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_step_in_targets

Read-onlyIdempotent

Get available step-in targets for the current stack frame, enabling selection of a specific function call when multiple share a line. Use with step_into(target_id=...) to enter the chosen target.

Instructions

Get available step-in targets for the current stack frame.

State: STOPPED required. Call before step_into(target_id=N) to choose target.

When multiple function calls exist on one line, this returns each one so you can choose which to enter via step_into(target_id=...).

Args: frame_id: Stack frame ID (uses current frame if omitted)

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": "get_step_in_targets"
  }
}

Input Schema

NameRequiredDescriptionDefault
frame_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already indicate readOnlyHint and idempotentHint. The description adds behavioral context: it requires STOPPED state and is used to choose a target. Does not contradict annotations.

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?

The description is concise with a clear structure: purpose, state requirement, usage, args, and escape hatch. Every sentence adds value.

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

Completeness5/5

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

Given no output schema, the description adequately explains what the tool returns (list of targets) and when it is useful. Also includes state dependency and alternative access via escape hatch.

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

Parameters4/5

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

Schema coverage is 0%, but the description explains the parameter 'frame_id' with default behavior: 'Stack frame ID (uses current frame if omitted)'. This adds meaning beyond the schema.

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 the tool's function: 'Get available step-in targets for the current stack frame.' This is a specific verb+resource tuple and distinguishes it from sibling tools like step_into, step_out, step_over.

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?

Explicitly advises when to use the tool ('Call before step_into(target_id=N)') and prerequisites ('State: STOPPED required'). Also mentions an escape hatch for advanced use.

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