Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

output_checkpoint

Idempotent

Mark the current output buffer position as a reference point, so subsequent assertions can verify only the output added after this checkpoint during debugging.

Instructions

Mark the current output buffer position for later assertions.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations declare idempotentHint=true and openWorldHint=false. The description adds minimal behavioral context ('Mark the current output buffer position') which is consistent but does not elaborate on side effects or state changes beyond what annotations imply.

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?

The description is a single sentence, making it concise, but it does not earn its place fully as it lacks crucial parameter details. It could be improved by integrating parameter explanation 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?

With no output schema and only one parameter, the description should fully explain the tool's purpose and parameter. It fails to cover the parameter's role, making the description incomplete for correct invocation.

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?

The input schema has one required parameter 'name' with no description and 0% schema coverage. The description does not explain what the name parameter represents or how to use it, leaving the agent with no guidance on parameter semantics.

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?

Description uses a specific verb-resource pair ('Mark the current output buffer position for later assertions') that clearly states the tool's function and distinguishes it from siblings like output_assert_since.

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

Usage Guidelines3/5

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

The description implies usage (to later assert about output) but does not explicitly state when to use or when not to, nor mention alternatives or prerequisites.

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