Skip to main content
Glama

find_calls

Read-onlyIdempotent

Trace outgoing function calls hop by hop to map dependencies and see what a function invokes. Adjust depth to control how many call levels to follow.

Instructions

What a function calls: outgoing calls, hop by hop.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the agent knows this is a safe, repeatable local read. The description adds only the notion of hop-by-hop traversal; it says nothing about the shape of the results, the meaning of a call edge, or truncation at the 200-item cap that the 'all' parameter hints at.

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?

It is a single short sentence with no padding, and the key scope term (outgoing) comes first. It is efficient, though its brevity leaves it close to under-specification rather than crisp specification.

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?

For a three-parameter graph query with full schema coverage and complete annotations, the description is minimally adequate. It does not clarify whether results are transitive call edges with depth controlling the expansion, nor what a returned 'call' consists of, leaving gaps that a more complete definition would close.

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 function, depth, and all are each documented in the schema itself, and the baseline is therefore 3. The description's 'hop by hop' loosely reinforces the depth parameter but adds no syntax, wildcard, or default details beyond what the schema already provides.

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

Purpose4/5

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

The description names a specific verb-and-resource pair: it lists the outgoing calls a function makes, traversed hop by hop. The word 'outgoing' implicitly separates it from the sibling find_callers (incoming callers), though no sibling is named outright.

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?

The phrase 'outgoing calls' implies when the tool is appropriate, as opposed to a reverse or caller lookup, and 'hop by hop' implies a transitive traversal. However, the description never states when to prefer it over find_callers or find_callchain, nor does it give any exclusions or prerequisites.

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