Skip to main content
Glama
Sign In
WinCode

WinCode

by linnnn89
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

wincode_diagnose_project

Diagnose project health, verify Windows/.NET SDK readiness, and inspect solution files to ensure development prerequisites are in place.

Instructions

Diagnoses project health, Windows/.NET SDK readiness, solution files, and development prerequisites.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must carry the behavioral disclosure burden. 'Diagnoses' implies a read-only analysis, but the description does not state whether the tool modifies anything, what environment checks it performs, whether it requires prerequisites, or what output it produces.

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?

The description is a single concise sentence that starts with the main action and immediately lists the key diagnostic targets. Every word adds meaning and there is no redundant filler.

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?

The description is minimally viable for a zero-argument tool: it names the diagnostic scope, but it lacks any indication of return values, output shape, or which sibling scenarios it is meant for. Since no output schema exists, more detail about what the agent should expect would improve completeness.

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?

The tool has zero parameters, so there is no parameter schema to clarify. The baseline of 4 applies because there is no param information the description needs to compensate for.

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 description uses a specific verb ('Diagnoses') and identifies concrete resources: project health, Windows/.NET SDK readiness, solution files, and development prerequisites. It is clear about what the tool inspects, though it does not explicitly differentiate itself from sibling tools like wincode_analyze_workspace.

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?

The description gives no guidance on when to use this tool versus alternatives. Sibling tools such as wincode_analyze_workspace and wincode_prepare_context could plausibly overlap in purpose, but no conditions or exclusions are provided.

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