WinCode
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workspace_openB | Opens and analyzes a project workspace directory. Identifies project type (dotnet, node, python, etc.), solution file, project count, primary language, git status, metadata, and file tree. |
| wincode_hello_worldA | Minimal connectivity and heartbeat verification tool for AI coding agents (Codex, Claude, etc.). Confirms WinCode Gateway is online. |
| wincode_analyze_workspaceA | High-level workspace and architecture analysis. Detects project types, .NET solutions, architecture layers, and key entry points without dumping raw files. |
| wincode_prepare_contextB | Prepares concise, high-semantic, decision-ready context snapshot for an agent task using Repomix and semantic distillation. Extracts relevant symbols, architectures, and packs essential files. |
| wincode_find_code_symbolA | Locates code symbols (classes, interfaces, methods, functions) across the workspace with signatures and line numbers (powered by Serena code intelligence). |
| wincode_find_referencesA | Finds all call sites and usages of a specified symbol across the repository. |
| analyze_change_impactA | Analyzes downstream blast radius, affected caller components, risk rating, and architectural decoupling recommendations before modifying code (AI change safety guard). |
| wincode_analyze_change_impactA | Alias for analyze_change_impact. Analyzes blast radius, affected callers, and risk rating before modifying code. |
| wincode_diagnose_projectB | Diagnoses project health, Windows/.NET SDK readiness, solution files, and development prerequisites. |
| wincode_plan_refactoringB | Provides structured refactoring guidance, step-by-step breakdown, and safety boundaries for a component. |
| wincode_safe_move_to_trashA | Safely moves an obsolete or deleted file into the project trash/ directory with metadata instead of permanent deletion. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Several tools have unclear boundaries: workspace_open and wincode_analyze_workspace both perform overlapping workspace/project analysis, and analyze_change_impact is duplicated by wincode_analyze_change_impact as an exact alias. This creates real misselection risk for agents.
Most tools follow a wincode_verb_noun convention, but workspace_open and analyze_change_impact break the prefix pattern. The alias pair wincode_analyze_change_impact/analyze_change_impact also mixes prefixed and unprefixed names for the same operation.
11 tools is a reasonable count for a coding-assistant workspace toolkit. However, the set is slightly padded by the alias duplicate and by two workspace-analysis tools that could likely be consolidated.
The toolset covers workspace analysis, symbol lookup, reference finding, change impact, diagnostics, refactoring planning, and safe deletion. It lacks direct file read/edit/build operations, but those may be intentionally outside its analysis-and-planning scope.