Skip to main content
Glama

get_method_overrides

Analyzes C++ virtual method overrides, showing base-class method overridden and derived-class overriding methods for a given method name.

Instructions

Return C++ virtual method override information — libclang-powered vtable analysis. Resolves virtual dispatch across class hierarchies: shows which base-class method this overrides, and which derived-class methods override this one. Text-based search cannot resolve virtual dispatch across translation units.

Shows what base-class method this method overrides, and what derived-class methods override this one. Built from the overrides table which is populated during fw-context index via post-processing of the inheritance graph and virtual method signatures.

For class-level inheritance, use get_inheritance_chain. For symbol details, use get_symbol_context.

Read-only. No side effects.

Args: method_name: Method name to get override information for. Use qualified name for disambiguation, e.g. 'UART_DRIVER::write'. project_root: Project root. Auto-detected if omitted.

Returns: dict: { name, qualified_name, kind, file, line, signature, overrides: [{usr, name, qualified_name, kind, file, line}], overridden_by: [{usr, name, qualified_name, kind, file, line}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
method_nameYesMethod name to get override information for. Use qualified name for disambiguation, e.g. 'UART_DRIVER::write'.
project_rootNoProject root. Auto-detected if omitted.
Behavior4/5

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

States 'Read-only. No side effects.' and explains the underlying data source (overrides table populated during indexing). While it covers safety and context, it doesn't mention potential error cases (e.g., method not found) or performance implications. Without annotations, it does a good job but could be more comprehensive.

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?

Well-structured with clear sections: purpose, detailed behavior, alternatives, side-effects, args, and returns. Every sentence serves a purpose. No redundancy. Concise yet comprehensive.

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?

Even without output schema, the description includes a detailed Returns section showing the exact dict structure with nested fields. Explains the process behind the data. All relevant aspects are covered for a tool with 2 parameters.

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%, with both parameters described. Description adds value for method_name by specifying qualified name format with example. For project_root, adds 'Auto-detected if omitted.' This provides useful context 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?

Description clearly states it returns C++ virtual method override information using libclang-powered vtable analysis. It specifies exactly what it shows: base-class method overridden and derived-class methods overriding. It distinguishes itself from sibling tools like get_inheritance_chain and get_symbol_context.

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 provides when-to-use guidance: for class-level inheritance use get_inheritance_chain, for symbol details use get_symbol_context. Also notes that text-based search cannot resolve virtual dispatch across translation units, helping agents understand limitations.

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