Skip to main content
Glama
Sign In

Umtri

by io.umtri
OverviewDiscussionsAdmin

Trace the blast radius of a node or bug

get_impact

Walks the connection graph (edges + apis) from a start node — or a bug's target — to find which other nodes a problem would reach. This is the tool for "if this breaks / I change this, what else do I need to check?" and for QA scoping. Impact does NOT always flow with the arrow. direction="affected" (default) answers "if the start breaks, who is hurt?" and follows: dependency edges backward (target→source), data_flow edges forward (source→target), apis backward (callee→caller). direction="dependsOn" is the reverse ("what does the start rely on?"). direction="both" unions them. See umtri://rules/system-structure (How problems propagate). Provide exactly one start: node (a node id) or bug (a bug id — starts from its target node, or both endpoints if the bug is on an api; ground-level bugs are rejected). Traversal is over CURRENT (live) structure only. Returns reached[] (each with hops distance, the node from which it was reached, and the connection via it came through — so you can reconstruct the chain), bugs[] (active bugs sitting on any reached node/api, worst score first), and coverage. IMPORTANT: the result is a list of nodes to CHECK, not a proven failure set — it is only as complete as the connections recorded. coverage.startsWithoutConnections flags when the start has no connections at all: an empty result then means "nothing recorded," not "nothing affected" — record edges/apis first.

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": {
      "slug": "<slug>"
    },
    "name": "get_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
bugNoStart from this bug's target. Provide this OR node.
nodeNoStart node id. Provide this OR bug.
slugYesGround slug.
maxDepthNoMax hops to traverse. Omit for unbounded.
directionNoaffected (default): what breaks if the start breaks. dependsOn: what the start relies on. both: union.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It goes far beyond the basics by explaining that impact does not always flow with the arrow, that traversal is over current live structure only, and that results are a list to check, not a proven failure set. It also documents the coverage.startsWithoutConnections edge case.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but well-structured and front-loaded. It starts with the core purpose, then details directions, returns, and caveats. Every sentence adds essential information—no filler or redundancy.

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

Completeness5/5

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

Given the tool's complexity and the absence of annotations and output schema, the description is remarkably complete. It explains the returned fields (reached[], bugs[], coverage), traversal semantics, limitations, and how to interpret empty results. It is self-contained for an agent to select and invoke it correctly.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant meaning beyond the schema. It explains direction's effect on edge traversal (e.g., 'dependency edges backward'), the exactly-one rule for node/bug, bug-as-target behavior, and what maxDepth and coverage flags mean. This makes parameter usage much clearer.

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

Purpose5/5

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

The description clearly states the action ('Walks the connection graph') and the resource ('edges + apis') with a specific goal ('find which other nodes a problem would reach'). It explicitly labels itself as 'the tool for' impact analysis, distinguishing it from sibling tools like get_graph.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit use cases ('if this breaks / I change this') and detailed direction semantics. It does not name an alternative tool to use instead, but the 'this is the tool' phrasing gives clear context. It also adds a constraint about exactly one start (node or bug) and ground-level bug rejection.

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

All Umtri toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources