Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

runtime_smoke_get_event_delta

Read-only

Fetch .NET debugging lifecycle events after a given cursor token, with optional event limit and agent mode, to track runtime changes during a debugging session.

Instructions

Return bounded lifecycle events after a cursor token.

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": {
      "cursor": "<cursor>"
    },
    "name": "runtime_smoke_get_event_delta"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorYes
agent_modeNo
event_limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, indicating safe read operation. The description adds that events are 'bounded' and 'lifecycle' and uses a cursor token, providing some behavioral context beyond annotations. However, it does not explain what 'bounded' means or how cursors work.

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 that efficiently conveys the core action. It is concise but could include additional context without becoming verbose.

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 tool with 3 parameters (including a nested cursor object), no output schema, and many siblings, the description is minimal. It does not explain 'lifecycle events', cursor semantics, return format, or error conditions, leaving the agent underinformed.

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 coverage is 0% (no parameter descriptions in schema), so the description must compensate. It only mentions 'cursor token' but fails to explain event_limit (default 50, max events) or agent_mode (default false, purpose unclear). The cursor object is left opaque.

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 ('Return') and resource ('bounded lifecycle events') with condition ('after a cursor token'). It is clear about what the tool does but does not differentiate from siblings like 'get_trace_delta' or 'runtime_smoke_tail_events'.

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 guidance on when to use this tool vs alternatives. There are many sibling tools with similar themes (e.g., runtime_smoke_tail_events, get_trace_delta, runtime_smoke_mark_event_cursor) but the description gives no context for selection.

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