Skip to main content
Glama

find_callees

Find call sites made from within a specific declaration using its indexed symbol ID and repository root; results include resolution quality.

Instructions

Finds indexed call sites made from within one declaration. Each result includes its resolution quality.

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": {
      "repository_root": "<repository_root>",
      "symbol_id": "<symbol_id>"
    },
    "name": "find_callees"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbol_idYesStable indexed symbol ID returned by outline_file or find_symbol.
repository_rootYesAbsolute path to the Git repository root to explore.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that results are indexed call sites and each includes resolution quality, but it does not describe error behavior, pagination, return fields, or whether traversal is shallow or transitive.

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?

Two short sentences with zero waste. The core purpose is front-loaded, and the second sentence adds relevant result-quality context.

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?

The tool has no annotations and no output schema, so the description should carry more return-shape and edge-case context. It gives a high-level result hint but leaves out what a result object contains beyond resolution quality and how unresolved or dynamic calls are handled.

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 the schema already explains both parameters. The description's phrase 'one declaration' slightly clarifies the intended symbol_id target, but it does not add format or constraint detail beyond the schema.

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 states a specific verb and resource: finds indexed call sites made from within one declaration. The phrase 'from within one declaration' gives directional scope that distinguishes it from find_callers and find_references without needing to name them.

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

Usage Guidelines3/5

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

Usage is implied by the definition: use it to find outgoing calls from a declaration. However, there is no explicit when-to-use versus alternatives such as find_callers, find_references, or find_symbol.

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