Skip to main content
Glama
Kirachon

Context Engine MCP Server

by Kirachon

Call Relationships

call_relationships
Read-onlyIdempotent

Explore static call graphs: retrieve direct callers and callees of any function or method in your codebase.

Instructions

Return deterministic local callers and/or callees of a known function or method symbol.

Use this tool when you need to:

  • See which functions invoke a given symbol (callers) and where

  • Inspect which identifiers a function invokes inside its own body (callees)

  • Complement symbol_definition (single declaration site) and symbol_references (non-declaration usages)

Caller heuristic: lines containing ( that are not declaration-like; the nearest enclosing declaration is reported as callerSymbol when detectable. Callee heuristic: locates the symbol's definition and scans the brace-delimited body for identifiers followed by '('. Brace-language only in v1; non-brace bodies (e.g., Python) yield empty callees.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
top_kNoMaximum entries per side (1-100). Defaults to 20.
symbolYesFunction or method identifier whose call relationships you want to inspect.
directionNoWhich side of the call graph to compute. Defaults to both.both
bypass_cacheNoWhen true, bypass caches for this call.
exclude_pathsNoOptional workspace-relative glob filters to exclude matching paths after include filtering.
include_pathsNoOptional workspace-relative glob filters to include matching paths only.
language_hintNoOptional language hint (currently advisory; reserved for future use).
workspacePathNoOptional workspace path. Defaults to the current workspace.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes
calleesYes
callersYes
metadataYes
directionYes
schema_versionYes
Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint. The description adds valuable behavioral details: the heuristic for callers and callees, brace-language limitation for callees, and that non-brace bodies yield empty callees. No contradiction.

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?

The description is well-structured with bullet points and front-loads the main action. It is slightly lengthy but every sentence earns its place by providing essential heuristic details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema (not shown but indicated), so return values are documented externally. The description explains heuristic limitations and complements siblings, providing sufficient context for a complex call-graph tool.

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?

Input schema has 8 parameters with 100% description coverage. The tool description does not add significant meaning beyond the schema, except for contextualizing the 'symbol' parameter via the heuristic explanation. Baseline 3 is appropriate.

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 it returns 'deterministic local callers and/or callees of a known function or method symbol.' It uses specific verbs (Return, See, Inspect) and distinguishes from siblings symbol_definition and symbol_references by noting they are complementary.

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

Usage Guidelines4/5

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

The description explicitly lists when to use (e.g., 'when you need to see which functions invoke a given symbol') and mentions complementing sibling tools. It does not explicitly state when not to use, but the context is sufficient for an agent to decide.

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/Kirachon/context-engine'

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