Skip to main content
Glama

ide_definition

Read-only

Resolve where an X++ element is defined in the open Visual Studio instance, listing every model, layer, module, and file containing it.

Instructions

Resolve where an element is defined according to the open Visual Studio: every model that defines it (with layer and module) and the element file in each.

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": {
      "type": "<type>",
      "name": "<name>"
    },
    "name": "ide_definition"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
typeYes

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
modelsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description usefully adds that results are derived from the currently open Visual Studio instance, which implies the answer is state-dependent and can be empty or partial if no solution is loaded. It also sketches the result shape (models with layer and module, element file per model), which goes beyond what annotations declare.

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 that states the action and the resolved output without filler. The colon-plus-clause construction is slightly dense but every clause adds information.

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?

An output schema exists, so return values needn't be explained, and the description's main missing pieces are parameter meaning and explicit routing versus lookup/search siblings. For a read-only two-parameter resolver this is adequate but leaves real gaps an agent must fill by trial.

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 must carry the load for the two required parameters, but it never mentions them. It gives no hint what 'type' means (element kind vs. model kind) or how 'name' relates to it, leaving the agent to guess at the constrained string fields.

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 where an element is defined') and resource, and scopes the answer to the open Visual Studio instance, returning defining models with layer/module plus the element file. This is clearly distinct from searching or listing, though it never names a sibling such as ide_references to sharpen the boundary.

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?

The phrasing 'where an element is defined' implies the navigation/go-to-definition use case, and 'according to the open Visual Studio' signals the prerequisite of a live IDE session. There is no explicit when-to-use/when-not guidance or named alternative for reference lookups, so the agent must infer the routing.

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