Skip to main content
Glama
Sign In
netcoredbg-mcp

netcoredbg-mcp

by thebtf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

ui_maximize_window

Maximize a top-level window using an optional partial title match, or target the main window when no title is provided. Enables GUI automation for .NET debugging.

Instructions

Maximize a top-level window via WindowPattern.

Args: window_title: Optional partial title match. Omit to target main window.

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

Input Schema

NameRequiredDescriptionDefault
window_titleNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.17.2

TDQS

A3.7/5.0
Behavior2/5

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

No annotations for readOnlyHint or destructiveHint, so description should disclose behavior. 'Maximize' implies mutation, but no details on side effects, permissions, or error conditions. Minimal disclosure beyond the action itself.

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?

Two sentences, front-loaded with purpose. No wasted words. Efficient and clear.

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?

Covers purpose and parameter usage adequately. Lacks details on failure modes (e.g., window not found) or return values. No output schema. Acceptable for a simple tool but could be more complete.

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 has 0% coverage (no descriptions), so description compensates by explaining window_title as 'Optional partial title match. Omit to target main window.' Adds clear meaning and default behavior.

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 clearly states 'Maximize a top-level window via WindowPattern' - specific verb (maximize) and resource (window). Distinguishes from sibling tools like ui_minimize_window and ui_restore_window by name and action.

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?

Provides guidance on parameter: 'Optional partial title match. Omit to target main window.' However, no explicit when to use vs alternatives or prerequisites are given. Implied usage but lacks exclusions.

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