Skip to main content
Glama

resolve_path

Read-only

Resolves an existing file or directory visible to the loaded Visual Studio solution so X++ tools can target the correct path before reads, writes, builds, or sync operations.

Instructions

Resolve an existing file or directory visible to the solution loaded in Visual Studio.

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

Input Schema

NameRequiredDescriptionDefault
pathYes
rootNo
operationNoread

Output Schema

NameRequiredDescriptionDefault
okYes
kindNo
pathNo
errorNo
operationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

C2.9/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 the useful constraint that the path must already exist, but it says nothing about failure behavior for non-existent or solution-external paths, nor about what the 'operation' mode actually triggers — notable given the schema offers write/build/endpointMutation modes that sit uneasily with a readOnly hint.

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 or redundancy. It is efficient, though its brevity is achieved at the cost of the missing detail noted elsewhere.

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

Completeness2/5

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

An output schema exists, so return values need not be described. However, for a three-parameter resolver with a non-obvious operation enum, the description leaves the key semantics undocumented and gives no guidance on path resolution rules, which is insufficient for correct invocation.

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% across three parameters, so the description carries the burden and does not meet it. It never explains 'path' format (absolute vs solution-relative), what 'root' selects, or the meaning and effect of the 'operation' enum values; only 'existing file or directory' loosely gestures at 'path'.

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?

States a specific verb (resolve) and resource (an existing file or directory) with a scoping qualifier (visible to the loaded solution). It is clear on its own, but it never distinguishes itself from plausible siblings such as reference_resolve or project_inspect, so an agent cannot route between them from this 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 when-not-to-use, and no named alternative. The only implicit hint is that the target must already exist and be visible to the solution, which an agent must infer rather than read.

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