Skip to main content
Glama

find_wrapper_callers

Identifies wrapper classes that call driver methods, revealing the adapter/wrapper architecture in C/C++ codebases.

Instructions

Find C/C++ wrapper classes that call methods of a driver class — libclang-powered adapter pattern detection. Traces method ownership across class boundaries to reveal the wrapper/adapter architecture (e.g. UART wraps UART_DRIVER). Text-based search cannot distinguish which class owns each method call.

Returns wrapper methods grouped by wrapper class, showing which driver methods each wrapper calls. Useful for understanding the adapter/wrapper architecture (e.g. UART wraps UART_DRIVER).

For the reverse perspective — finding who calls a specific driver method — use find_callers. For class member listing use get_class_members.

Read-only. No side effects. Requires the reference index (fw-context index — refs on by default).

Args: class_name: Driver class name to find wrappers for. E.g. 'UART_DRIVER' or 'hal::UART_DRIVER'. project_root: Project root. Auto-detected if omitted. limit: Maximum wrapper method results (default 50).

Returns: list of dicts, each with: wrapper_class (str), method_count (int), methods (list of dicts — each with method, qualified_name, kind, and calls (list of driver methods called)).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum wrapper method results (default 50).
class_nameYesDriver class name to find wrappers for. E.g. 'UART_DRIVER' or 'hal::UART_DRIVER'.
project_rootNoProject root. Auto-detected if omitted.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description declares 'Read-only. No side effects.' and explains the mechanism (libclang-powered). No contradictions.

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?

Well-structured with paragraphs, examples, and bullet points. Front-loaded with main purpose. Some redundancy in explaining adapter pattern twice, but still efficient.

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?

Given complexity of adapter pattern detection and that output schema is described in Returns, the description is comprehensive: purpose, mechanism, usage guidelines, parameters, and return format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds example values, auto-detection for project_root, default for limit, and context beyond 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 clearly states the tool finds C/C++ wrapper classes calling methods of a driver class, uses libclang for adapter pattern detection, and provides examples like 'UART wraps UART_DRIVER'. It distinguishes from text search and sibling tools.

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?

Explicitly states when to use: 'For the reverse perspective — use find_callers. For class member listing use get_class_members.' Also mentions read-only and index requirement.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/turbyho/fw-context-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server