Skip to main content
Glama

find_callchain

Read-onlyIdempotent

Trace how one function or method reaches another, and return the module path when no call path exists, to map code dependencies.

Instructions

A call path from one function to another, or a module path when no call path exists.

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": {
      "source": "<source>",
      "target": "<target>"
    },
    "name": "find_callchain"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoList everything instead of stopping at 200 items.
depthNoHow many hops to follow.
sourceYesFunction or method name; literal text with optional .* wildcards.
targetYesFunction or method name; literal text with optional .* wildcards.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description does add one genuinely useful behavioral fact beyond that: the fallback to a module path when no call path exists. It omits the 200-item truncation and the path output format, but with annotations carrying the safety burden a 3 is appropriate.

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?

One sentence with no padding, and the main result (call path) is front-loaded before the fallback clause. The sentence is a noun fragment rather than a statement of action, which slightly reduces clarity without adding waste.

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?

With four parameters, full schema coverage, rich annotations, and no output schema, the description covers the fallback case but leaves the shape of the returned path undefined – depth of detail, ordering, and truncation at 200 items go unmentioned. Reasonably complete for the structured data supplied, but thin for a path-traversal tool where result shape is the main uncertainty.

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 source, target, depth, and all are already documented with defaults, bounds, and wildcard syntax. The description adds no meaning beyond the schema – it does not even mention that source and target accept '.*' wildcards, though the schema covers that. Baseline 3 holds.

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

Purpose3/5

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

The description states the resource returned ('a call path from one function to another') but never supplies an action verb, so it reads as a description of output rather than of what the tool does. The 'find_' name prefix and the sibling set hint at a lookup, but the description itself does not distinguish it from find_calls, find_callers, or find_function.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites, and no routing toward or away from any alternative. The clause about a module path fallback describes output behavior, not a usage condition, so an agent gets no help choosing between this and find_calls.

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