Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_scroll

Scroll a UI control by its automation ID. Specify direction (up, down, left, right) and amount; resume the app from breakpoints first if necessary.

Instructions

Scroll a UI control.

Note: If app is STOPPED at breakpoint, resume with continue_execution() first.

Args: automation_id: AutomationId of the scrollable control direction: "up", "down", "left", "right" amount: Number of scroll units (default 3)

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

Input Schema

NameRequiredDescriptionDefault
amountNo
directionNodown
automation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

A4/5.0
Behavior3/5

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

No annotations beyond openWorldHint=false, which the description does not contradict. The description lacks details on side effects, error behavior, or whether scrolling is synchronous. Provides minimal behavioral insight.

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 concise (two lines plus args list) and front-loaded with purpose. The note about breakpoints is relevant. Could be slightly more structured but efficient.

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

Completeness3/5

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

For a simple tool without output schema, the description covers basic usage but lacks details on failure modes or prerequisites for scrollable controls. It is minimally adequate.

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?

With 0% schema coverage, the description adds meaning by explaining automation_id, direction (listing values), and amount (noting default). However, it omits the default value for direction (which is 'down' in schema), leaving a small gap.

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 'Scroll a UI control' with a specific verb and resource. Among numerous sibling UI tools (e.g., ui_click, ui_drag), it uniquely identifies scrolling behavior.

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?

Provides a clear prerequisite: if the app is stopped at a breakpoint, resume with continue_execution() first. Does not explicitly distinguish from alternatives like ui_collapse or ui_expand, but the context is adequate.

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