Skip to main content
Glama

ide_solution_projects

Read-only

Lists the projects and models of the solution open in Visual Studio as the IDE sees them, so you can inspect solution structure and target the right project.

Instructions

List the projects (and their models) of the solution open in Visual Studio, as the IDE sees them.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
modelsNo
projectsNo
solutionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact — the results reflect the IDE's live view rather than file-based scanning — but says nothing about failure behavior when no solution is open or how the models are nested in the result.

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?

A single sentence with no filler, front-loaded with the verb and resource. The parenthetical about models and the trailing qualifier both add information rather than padding.

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

Completeness4/5

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

For a parameterless read tool with an output schema and read-only annotations, the description covers what is returned at a high level and where the data comes from. The main residual gap is the precondition/error case when the IDE has no solution loaded.

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 takes zero parameters, so there is no parameter meaning to convey and no schema gap to compensate for. Baseline 4 applies.

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?

Specific verb ('List') plus a specific resource ('projects (and their models) of the solution open in Visual Studio'), and the qualifier 'as the IDE sees them' pins the scope to live IDE state. It does not name a sibling such as ide_project_items or solution_inspect, so an agent must infer the boundary itself.

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?

Usage is only implied: the phrase 'solution open in Visual Studio' signals the tool applies to the active IDE session. There is no explicit when-to-use, no statement of preconditions (e.g. a solution must be loaded), and no routing to alternatives like project_inspect for on-disk data.

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