Skip to main content
Glama
Sign In
Venira

Venira

by N0moreher0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Change impact

project_change_impact
Read-onlyIdempotent

Identify files, symbols, and tests affected by planned code changes so you know what to read and which tests to run before renaming or editing.

Instructions

List the files and symbols affected by changing given files or symbols (direction: dependents, dependencies or both). At least one of files/symbols; a symbol seed takes {name, relative_path} (file is an alias). Use when: you are about to rename or change something and need which files to read and which tests to run. Avoid when: you want the whole graph (project_dependency_graph). Output: affected[] {id, distance, path, confidence}, summary {affected_files, affected_symbols, tests_affected}, unresolved[].

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_change_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoMax hops from the seeds (default 5).
filesNoWorkspace paths you plan to edit. At least one of files/symbols is required.
formatNoOutput format (default json).
symbolsNoSymbols you plan to rename/change; pass a name, or {name, relative_path} (or {name, file}) when the name is ambiguous. At least one of files/symbols is required.
directionNoTraversal direction (default dependents).
max_nodesNoMax affected files (default 300).
include_testsNo1 includes test files (default) and counts them in tests_affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.21.0
    • changedInput schema / properties / depth / description
      Previous value: -"BFS hop cap (default 5)."New value: +"Max hops from the seeds (default 5)."
    • changedInput schema / properties / files / description
      Previous value: -"Workspace paths you plan to edit."New value: +"Workspace paths you plan to edit. At least one of files/symbols is required."
    • changedInput schema / properties / symbols / description
      Previous value: -"Symbols you plan to rename/change; pass a name, or {name, file} when the name is ambiguous."New value: +"Symbols you plan to rename/change; pass a name, or {name, relative_path} (or {name, file}) when the name is ambiguous. At least one of files/symbols is required."
    • changedInput schema / properties / symbols / items / anyOf
      Previous value: -[
-  {
-    "maxLength": 200,
-    "type": "string"
-  },
-  {
-    "properties": {
-      "file": {
-        "maxLength": 500,
-        "type": "string"
-      },
-      "name": {
-        "maxLength": 200,
-        "type": "string"
-      },
-      "relative_path": {
-        "maxLength": 500,
-        "type": "string"
-      }
-    },
-    "required": [
-      "name"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "maxLength": 200,
+    "type": "string"
+  },
+  {
+    "properties": {
+      "file": {
+        "description": "Alias of relative_path (relative_path wins when both are given).",
+        "maxLength": 500,
+        "type": "string"
+      },
+      "name": {
+        "description": "Symbol name.",
+        "maxLength": 200,
+        "type": "string"
+      },
+      "relative_path": {
+        "description": "File the symbol is declared in; preferred over file.",
+        "maxLength": 500,
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  }
+]
  2. Addedv1.13.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world scope, so the safety profile is free. The description adds useful behavior beyond that: seed preconditions ('At least one of files/symbols'), the symbol seed shape, and an unresolved[] output channel that signals the graph may not fully resolve seeds. It does not explain what confidence means or what happens at the max_nodes ceiling, so it stops short of 5.

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 front-loaded with the core action, then cleanly segmented into seed requirements, use/avoid conditions, and output shape. Every clause carries information; there is no restating of the tool name or filler prose.

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?

With seven parameters and no output schema, the description compensates well by enumerating the return shape (affected[], summary counts, unresolved[]). Seed requirements and defaults are covered via the schema. The only gap is behavior at the max_nodes cap (truncation signaling), which an agent would want to know before relying on a 300-file default.

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 every parameter (depth, files, symbols, direction, max_nodes, include_tests, format) is already documented in structured data. The description adds only the symbol seed shape and file/relative_path alias note, which the schema also states, so it does not meaningfully exceed the schema's own semantics.

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 opens with a specific verb and resource: 'List the files and symbols affected by changing given files or symbols', and immediately qualifies scope with the direction option. It names the sibling it is not (project_dependency_graph) for whole-graph queries, so an agent can distinguish the two without opening either schema.

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

Usage Guidelines5/5

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

It provides explicit 'Use when' guidance tied to the concrete scenario of renaming/changing code and needing files to read and tests to run, plus an 'Avoid when' that names the alternative tool. Both the positive and negative cases are stated, leaving nothing to inference.

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