Skip to main content
Glama

ide_type_relations

Read-only

Retrieves class relationships from the open Visual Studio: base inheritance chain, derived classes, interface implementers, or classes carrying an attribute.

Instructions

Class relationships from the open Visual Studio: bases (inheritance chain), derived (classes extending it), implementers (classes implementing an interface) or attributed (classes carrying an attribute).

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": {
      "relation": "<relation>",
      "name": "<name>"
    },
    "name": "ide_type_relations"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
limitNo
relationYes

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
namesNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

B3.4/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 safety and locality are covered. The description adds useful context that results come from the currently open Visual Studio instance, but says nothing about pagination/truncation despite a limit parameter, whether a solution must be loaded, or what happens when the type name is not found.

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 dense sentence that front-loads the resource and immediately defines each relation mode, with no filler. The repeated word 'classes' in the glosses is slightly redundant but aids clarity rather than hurting it.

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-value explanation is not needed, and the four relation modes are well defined. However, for a tool that maps to a live IDE session, the definition omits preconditions (solution loaded, language/symbol scope) and the meaning of name and limit, leaving real gaps an agent would hit at call time.

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

Parameters3/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 parameter meaning. It does an excellent job on the relation enum, glossing all four values, but leaves the required name parameter (whose type? qualified or short name?) and the limit parameter entirely unexplained, covering only one of three parameters.

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?

The description names the resource precisely (class relationships) and scopes it to 'the open Visual Studio', then enumerates the four relation kinds with a short gloss each. An agent can tell this apart from ide_references or ide_definition because it is about type-to-type edges, not symbol lookup, though the description never explicitly contrasts them.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternatives are named. Usage is only implied by the enumeration of relation modes (bases for inheritance chain, derived for extenders, implementers for interfaces, attributed for attribute carriers), which helps pick the relation argument but not whether this tool is the right one at all.

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