Skip to main content
Glama

reference_impact

Read-only

Traverse bounded incoming dependents or outgoing dependencies at artifact granularity to assess change impact and identify affected X++ artifacts.

Instructions

Traverse bounded incoming dependents or outgoing dependencies at artifact granularity.

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": {
      "id": "<id>"
    },
    "name": "reference_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
depthNo
limitNo
directionNoincoming

Output Schema

NameRequiredDescriptionDefault
okYes
errorNo
itemsNo
freshnessNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already disclose readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds only the vague qualifier 'bounded' and says nothing about traversal semantics such as cycle handling, whether results are paginated, or how truncation at depth/limit behaves.

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 terseness comes at the cost of clarity rather than being genuinely dense with information.

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 needn't be explained, but with 0% parameter coverage and no usage guidance, an agent still cannot determine when to choose this traversal over the sibling reference_tree or reference_graph tools, nor what the depth/limit knobs actually control.

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% for four parameters, so the description must carry the burden and largely fails: 'incoming/outgoing' mirrors the direction enum, and 'bounded' hints at depth/limit without explaining what depth counts or what the limit truncates. The required 'id' parameter and its acceptable forms are never addressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb ('traverse') and resource ('incoming dependents or outgoing dependencies') are stated, but 'artifact granularity' is unexplained jargon and the sentence largely restates the direction enum. Nothing distinguishes it from siblings like reference_graph, reference_tree, or reference_extensions, so an agent cannot confidently pick it out of the catalog.

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 or when-not-to-use guidance and no named alternative among the many graph/reference siblings. The agent is left to infer that this is a bounded traversal rather than a full graph dump.

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