Skip to main content
Glama
Sign In
windows-debug-mcp

windows-debug-mcp

by emyk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_network_configuration

Retrieve network adapter details, IP configuration, and latency-critical settings like interrupt moderation and TCP auto-tuning to diagnose network-related performance issues on Windows.

Instructions

Network adapters, drivers, IP configuration and the latency-relevant settings.

Interrupt moderation, energy-efficient Ethernet, receive-side scaling and TCP auto-tuning all show up here; they matter for online play far more than raw bandwidth does.

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

Input Schema

NameRequiredDescriptionDefault
include_advancedNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

No annotations provided, so description must disclose behavior. It mentions specific config categories (interrupt moderation, etc.), suggesting read-only intent. However, it does not explicitly state that the tool is non-destructive or list any side effects.

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?

Description is brief (two sentences) but front-loads key information. The first sentence lists main items, but could be more structured (e.g., bullet list). Minimal waste, though slightly informal.

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?

Output schema exists, so return values are covered. However, the description omits when to set include_advanced to false or any prerequisites. For a simple tool with one optional parameter, it is adequate but not comprehensive.

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 explanation of the 'include_advanced' parameter. With only one parameter, the description should clarify its effect, but it does not, leaving the agent to rely solely on the schema.

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?

Description clearly states what tool retrieves (network adapters, drivers, IP configuration, latency-relevant settings) and provides specific examples. However, it lacks explicit differentiation from siblings and the informal tone slightly reduces clarity.

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 explicit guidance on when to use this tool or when not to. The description implies relevance for gaming/performance but does not state alternatives or exclusion criteria. Sibling tools are listed but not compared.

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