Skip to main content
Glama

solution_inspect

Read-only

Enumerates and validates X++ and other projects inside a Visual Studio .sln file, so you can confirm solution contents before editing, building, or syncing.

Instructions

Enumerate and validate X++ and other projects in a Visual Studio .sln file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "solution_inspect"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo

Output Schema

NameRequiredDescriptionDefault
okYes
pathNo
errorNo
validNo
sha256No
projectsNo
diagnosticsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3/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 and the description only needs to add value. "Validate" hints at a diagnostic behavior beyond plain enumeration, but it never says what validation checks, whether failures are reported as errors or data, or how deep the traversal goes. Since an output schema exists, return-shape disclosure is not required, but the validation semantics remain unexplained.

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?

A single front-loaded sentence with no filler. It is efficient, though the brevity is partly the cause of the missing usage and parameter context rather than a sign of tight curation.

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 output schema removes the need to describe return values, and annotations cover safety, so the minimum bar is met. However, for a two-parameter inspection tool with zero schema documentation, omitting all explanation of path versus root and all guidance on when to prefer this over project_inspect leaves real gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for two parameters — and it explains neither. The distinction between the required "path" (presumably the .sln file) and the optional "root" is completely undefined, forcing the agent to guess at meaning and expected format.

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?

"Enumerate and validate X++ and other projects in a Visual Studio .sln file" names a specific verb pair (enumerate, validate) and a concrete resource (projects in a .sln). It is clear what the tool does, but it never distinguishes itself from near-neighbors such as project_inspect or ide_solution_projects, so an agent cannot choose between them from the text alone.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The agent is left to infer that this is the solution-level entry point rather than the project-level one, which is exactly the ambiguity the sibling list creates.

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