Skip to main content
Glama

What depends on a function

graph_impact
Read-only

Find every function and class that calls a given name, grouped by call distance, plus the tests that reach it. Use before changing a signature or behaviour.

Instructions

Everything in the repository that calls a function or class, directly or through other code, grouped by distance, plus the tests that reach it. Use it before changing a signature or behaviour. Returns JSON. Read-only and local.

Works without SKYLOS_API_KEY and has no daily limit: it reads the repository on this machine and sends nothing to Skylos Cloud.

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

Input Schema

NameRequiredDescriptionDefault
nameYesGraph id, dotted name, short name, or path::Name
pathNoProject directory. A relative path resolves against the MCP server's working directory..
depthNoHow many calls up to follow, 1-8

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.6.0

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing operational facts an agent needs: it runs locally, sends nothing to Skylos Cloud, requires no API key, and has no daily limit. Those are exactly the constraints that would otherwise cause an agent to avoid or misuse a read tool.

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?

Front-loads the result definition, then the usage trigger, then operational caveats - a sensible order. 'Returns JSON' is mild filler given an output schema exists, but nothing else is wasted.

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?

Output shape is covered by an existing output schema and safety by annotations, so the description only needed to add scoping and environment facts, which it does. An agent has everything required to decide and call it correctly.

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 coverage is 100%, so the schema already documents name, path, and depth including the 1-8 range and the relative-path resolution rule. The description mentions grouping by distance but 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 and resource: everything that calls a function or class, direct or transitive, grouped by distance, plus reaching tests. That is a concrete result shape an agent can distinguish from graph_find or graph_describe 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 Guidelines4/5

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

Gives an explicit trigger: 'Use it before changing a signature or behaviour.' That ties the tool to a clear decision point. It does not name an alternative tool or a when-not condition, so it stops short of full routing guidance.

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