Skip to main content
Glama

load_solution

Load a .NET solution file (.sln/.slnx) to make it the active workspace. Optionally filter which projects to include using glob patterns or exact names.

Instructions

Load a .sln/.slnx solution at runtime and make it the active solution. Both include and rootProjects match against the project FILE NAME without extension (the .csproj/.vbproj base name), NOT the assembly name. Pass include (case-insensitive glob array, supporting only * and ? wildcards — character classes like [...] are NOT supported) or rootProjects (EXACT, case-sensitive file names) to load only a subset; the loader walks ProjectReference transitively from those seeds to keep the workspace semantically complete. A filter that matches NO project is an ERROR (the call fails) — it does NOT silently fall back to a full load; if unsure of exact names, do a no-filter load first and call list_solutions to discover them. If the same path is already loaded, providing a new filter disposes the previous workspace (replace semantics). If the solution is already loaded with no filter, it simply activates it (~instant). New solutions take ~3 seconds to load and compile. For very large solutions (hundreds of projects) that take minutes to open, pass background: true to return a taskId immediately instead of blocking; poll it with get_task_status until it succeeds (its result carries the loaded/skipped counts). The new solution only becomes active once the background load finishes, so other tools keep working against the current solution meanwhile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesFull path to the .sln or .slnx file to load
includeNoOptional case-insensitive glob patterns against project file name without extension (e.g. 'MyApp.*')
backgroundNoIf true, load on a background task and return a taskId immediately (poll with get_task_status) instead of blocking until the solution is ready. Default false.
rootProjectsNoOptional exact project file names without extension; both arrays act as seeds for a transitive ProjectReference closure
Behavior5/5

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

No annotations provided, so the description carries full burden. It thoroughly discloses: runtime loading, filter matching rules (case-insensitive glob vs exact case-sensitive), transitive closure, error on no match, replace semantics, instant activation for already-loaded solutions without filter, typical load time, background mode behavior, and activation timing. This goes well beyond minimal requirements.

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 a single paragraph but well-structured with clear sentences. It front-loads the main purpose and then details. While it is somewhat lengthy, every sentence adds necessary information for correct usage. Could benefit from bullet points for scanning, but current format is acceptable.

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

Completeness5/5

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

Given no output schema, the description fully covers error cases (no match), background task polling, activation behavior, and replaces and activate semantics. It also references related tools (list_solutions, get_task_status). This is highly complete for a tool with 4 parameters and complex behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value by explaining matching rules for include (only * and ?, case-insensitive) and rootProjects (exact, case-sensitive), the interaction between the two filters, the transitive closure, and the behavior of background mode. This is more than what the schema provides.

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 the tool loads a solution file and makes it active, with specific details on filtering and background loading. It distinguishes from sibling tools like unload_solution and set_active_solution by describing its unique behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance, including when to use filters, when to use background mode, and what happens on errors. It also gives an alternative strategy (do a no-filter load first and use list_solutions) for uncertain naming, and explains the replace-activate semantics for already-loaded solutions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MarcelRoozekrans/roslyn-codelens-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server