Skip to main content
Glama
opsmill

infrahub-mcp

Official
by opsmill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Find Reachable

find_reachable
Read-only

Find nodes of specified kinds reachable from a source to map dependencies and blast radius. Use it for impact analysis and to see what connects to or depends on an object.

Instructions

Find nodes of the given kinds reachable from a source node (impact analysis).

Use this to answer "what depends on / is connected to this object?" — for blast-radius and dependency discovery. Requires Infrahub 1.10+.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
branchNoBranch to query. Defaults to the default branch.
sourceYesSource node: a UUID or kind-qualified HFID.
max_depthNoMaximum traversal depth (1-30).
max_resultsNoMaximum distinct reachable nodes to return (1-200).
target_kindsYesNode kinds to search for, reachable from the source.
shortest_paths_onlyNoReturn only the shortest path to each target.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.2.0
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Addedv1.1.7

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds genuinely useful context beyond that: the version requirement (Infrahub 1.10+) and the analytical semantics of traversal. It does not discuss result limits or traversal cost, which max_depth/max_results imply matter.

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?

Three short sentences, front-loaded with the core action, then the use case, then the prerequisite. No filler.

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

Completeness4/5

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

For a 6-parameter read-only traversal tool with no output schema, the description covers purpose, use case, and version prerequisite, which is enough to call it correctly. It is slightly thin on what a result actually contains (nodes vs paths, shortest-path behavior), which would help given the absent output schema.

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 100%, so all six parameters including ranges (1-30 depth, 1-200 results) and defaults are already documented. The description only implicitly references source and target_kinds ('given kinds', 'source node') and adds no format or syntax detail beyond the schema, so baseline 3 applies.

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?

States a specific verb+resource with scope: 'Find nodes of the given kinds reachable from a source node'. The parenthetical '(impact analysis)' anchors the intent, and it is distinguishable from the sibling find_paths because it returns reachable nodes rather than paths.

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?

Gives clear usage context — 'what depends on / is connected to this object?', blast-radius and dependency discovery — which tells the agent when this tool is the right pick. It does not name alternatives such as find_paths explicitly or state when not to use it, so it falls short of a 5.

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

Deploy Server

Other Tools