Skip to main content
Glama
harshithsunku

mcp-gtags-server

by harshithsunku
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Call-path reachability

reachability
Read-only

Determine whether one function can transitively call another and find the shortest call chain with file:line call sites, using BFS over the caller graph.

Instructions

Call path / call chain: does FROM transitively call TO, and through which functions?

Use this instead of chaining find_callers rounds when the question is "can this function end up in that one?". BFS over the caller graph returns the SHORTEST chain, each hop with the call site's file:line. JSON results: {path_found, hops, depth, nodes_explored}; hops run from from_symbol to to_symbol. Static analysis cannot follow function pointers (ops structs, callbacks).

Args: from_symbol: The caller end ("can this reach ..."). to_symbol: The callee end ("... this function?"). max_depth: Longest chain to consider, in calls (1-12, default 8).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNotext
max_depthNo
to_symbolYes
from_symbolYes
project_rootNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / properties / format / default
      Previous value: -"json"New value: +"text"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "reachabilityOutput",
-  "type": "object"
-}New value: +null
  2. Addedv1.1.0

TDQS

A4.6/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: BFS over the caller graph, shortest-chain semantics, per-hop call-site file:line details, result fields, hop direction, and the limitation that function pointers cannot be followed. This is exactly the kind of context an agent needs.

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?

The description is efficient and front-loaded, opening with the core question and then adding usage, behavior, limitations, and parameter details. No sentence is wasted, and the argument explanations are compact and meaningful.

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 description is largely complete: it covers purpose, alternative usage, output shape, direction of hops, depth limits, and a key limitation. It does not mention the text output format or project_root, but the required behavior and main arguments are fully specified, so the gaps are minor.

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 0%, so the description carries the burden. It usefully explains from_symbol, to_symbol, and max_depth, but it does not explain format or project_root, both of which appear in the schema. The main parameters are well covered, but the full parameter set is not.

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 a specific verb and resource: it determines whether FROM transitively calls TO and identifies the chain of functions. It also explicitly differentiates itself from find_callers, and the 'shortest chain' detail sharpens the scope.

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?

It gives explicit guidance: use this instead of chaining find_callers rounds when the question is whether one function can end up in another. This directly routes the agent to the correct sibling and explains the intended use case.

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

Deploy Server

Other Tools