Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

runtime_smoke_tail_events

Read-only

Retrieve bounded lifecycle events for a given smoke test run ID. Use after_cursor and limit to paginate through event history, enabling monitoring of runtime smoke test execution.

Instructions

Tail bounded lifecycle events for a durable runtime smoke run.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
run_idYes
after_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, making safety clear. The description adds 'tail' and 'bounded' but does not explain behavior like pagination, blocking, or what constitutes 'bounded.' No conflicts with annotations.

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, which is concise but lacks essential structure. It omits parameter explanations and usage context, making it too sparse for a tool with 3 parameters and no output schema.

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 no output schema and 0% parameter documentation, the description should explain the return format and parameter semantics. It fails to provide enough context for an agent to invoke the tool correctly.

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?

Schema coverage is 0%, and the description provides no parameter details. It does not explain run_id, after_cursor, or limit, leaving the agent to infer from schema names alone. This is insufficient for correct usage.

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 verb 'Tail' and resource 'bounded lifecycle events' clearly indicate the tool's function. It distinguishes itself from sibling tools like runtime_smoke_get_event_delta by implying continuous/paginated retrieval rather than a single snapshot. However, the term 'bounded' is ambiguous without context.

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 is provided on when to use this tool versus alternatives (e.g., runtime_smoke_get_event_delta or runtime_smoke_get_result). The description does not mention prerequisites, context, or exclusion criteria.

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