Skip to main content
Glama

impact_analysis

Read-onlyIdempotent

Identify every asset affected when a given asset fails, including the dependency path that proves each impact.

Instructions

What stops working if this asset stops? Returns every impacted asset with the dependency path that proves it.

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": {
      "asset": "<asset>"
    },
    "name": "impact_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYes
max_depthNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description's added value is that results are evidence-bearing, returning the dependency path alongside each impacted asset, which tells the agent the output is verifiable rather than a bare list. It says nothing about traversal depth semantics, performance on large graphs, or whether results are truncated.

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?

Two sentences with no filler, opening with the motivating question and immediately following with what is returned. Front-loading is good. The interrogative framing is slightly indirect compared to a declarative statement of purpose, but it earns its place by conveying intent compactly.

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 the description need not explain return fields, and it reasonably does not. The remaining gap is the input side: with 0% schema coverage on both parameters and a depth-bounded traversal, an agent cannot tell how to form the asset argument or how max_depth changes results. Adequate but incomplete for a graph traversal tool.

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 two parameters, so the description carries the full burden of explaining them and does not. It never clarifies what form 'asset' takes (identifier, name, URN) or what 'max_depth' controls and how the default of 6 bounds the traversal. The only implicit signal is 'every impacted asset', which hints at transitive reachability but gives no parameter-level guidance.

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 states a specific operation: given an asset, return every impacted asset plus the dependency path proving the impact. That is a clear verb+resource framing that an agent can distinguish from a forward-looking search or a root-cause tool. It stops short of naming any sibling explicitly, so differentiation is inferential rather than stated.

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 framing question 'What stops working if this asset stops?' implies the use case — downstream impact of removal or failure — which is useful context. However, there is no explicit when-to-use versus when-not, no mention of the inverse direction (root cause), and no prerequisites such as the asset needing to exist in the graph.

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