Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Capabilities

Features and capabilities supported by this server

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
gograph_apiA

Extract the public API surface of a Go package, listing all exported functions, types, and interfaces. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when building integration layers, documenting public interfaces, or verifying exports. Do NOT use for private/unexported symbols (use gograph_node instead). COMPLETENESS: Requires 'package' parameter. Returns a clean summary of exported package API symbols. Example package: 'internal/search'.

gograph_arityA

Identify functions or methods that exceed a specified number of parameters (arity violation). BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to audit design parameters or identify functions that should be refactored into a parameter struct. Do NOT use for struct fields (use gograph_fields instead). COMPLETENESS: Optional 'threshold' value (defaults to 5). Returns a list of functions exceeding the target parameter count.

gograph_boundariesA

Verify package architecture constraints against boundaries.json to detect forbidden imports and illegal layer dependencies. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to check if packages conform to domain design constraints or to debug illegal import cycles and layered violations. Do NOT use for general dependency mapping (use gograph_deps instead). COMPLETENESS: Optional 'config' path. Returns a structured boundary compliance report listing authorized vs unauthorized dependencies.

gograph_calleesA

Find and list all downstream functions or methods invoked from inside the specified caller function. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when you need to understand the downstream execution flow, dependencies, and external calls of a single function. Do NOT use if you want upstream callers (use gograph_callers instead). COMPLETENESS: Requires 'function' parameter. Returns a complete array of callees, including their package paths and signatures. Example function: 'Serve'.

gograph_callersA

Find and list all functions or methods that call the specified target function. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when performing impact analysis, tracing call hierarchies, or identifying who consumes a particular API. Do NOT use if you want downstream callees (use gograph_callees instead). COMPLETENESS: Requires 'function' parameter. Returns a structured list of calling function symbols and their exact file locations. Example function: 'BuildGraph'.

gograph_capabilitiesA

Discover the available gograph MCP tools, their purposes, recommended workflows, and limitations. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool first to understand what gograph can do. Do NOT call this tool repeatedly once capabilities are cached. COMPLETENESS: Returns a structured checklist of all 50 available tools, recommended agent workflows, and limitations.

gograph_changesA

Analyze structural changes and modifications in Go files compared to a specific git commit reference. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool during code reviews, pull request verification, or post-edit sessions to track structural diffs. Do NOT use for line diffs (use standard git diff instead). COMPLETENESS: Requires 'since' parameter. Returns changed symbol names, kinds, and paths. Example since: 'HEAD~1'.

gograph_complexityA

Estimate and report cyclomatic complexity metrics for Go functions, sorted from highest to lowest. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when auditing code quality, identifying high-maintenance functions, or planning refactoring of complex logic. Do NOT use for import dependency metrics (use gograph_deps instead). COMPLETENESS: Optional 'symbol' filter. Returns a structured complexity report indicating complexity numbers and severity labels. Example symbol: 'Build'.

gograph_concurrencyA

Scan the codebase to locate all concurrency declarations (go channels, select statements, sync primitives, go routines). BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to trace asynchronous routines, verify race safety, or audit synchronization primitives. Do NOT use for standard linear execution flows. COMPLETENESS: Returns file locations, line coordinates, and types of all concurrency primitives detected.

gograph_constructorsA

Find factory and constructor functions that instantiate and return the specified Go struct. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when auditing object initialization patterns, looking for existing builder functions, or verifying correct struct instantiation. Do NOT use if you need struct fields (use gograph_fields instead). COMPLETENESS: Requires 'struct' parameter. Returns a detailed list of constructor function symbols, their file locations, and signatures, showing exactly how the target struct is built. Example struct: 'Graph'.

gograph_contextA

Build a highly condensed diagnostic context file for a set of target Go packages or symbols. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to summarize multiple packages for LLM consumption, reducing token overhead. Do NOT use for deep line-by-line reading (use gograph_source instead). COMPLETENESS: Returns a compact text summary of package structures, exported APIs, and type definitions. Example package: 'internal/search'.

gograph_couplingA

Assess structural coupling and dependency ratios (Afferent vs Efferent coupling) for Go packages. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to evaluate package isolation, modularity strength, and stability indexes. Do NOT use for single function analysis (use gograph_complexity instead). COMPLETENESS: Returns afferent coupling (Ca), efferent coupling (Ce), and instability ratio (I) per package.

gograph_dependentsA

Find all downstream packages that depend on or import the specified target package. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to identify downstream impact before changing a public package interface. Do NOT use for direct callers of a single function (use gograph_callers instead). COMPLETENESS: Requires 'package' parameter. Returns concrete packages importing the target package. Example package: 'internal/graph'.

gograph_depsA

Render the package import dependency tree for a target Go package. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when mapping package interactions, auditing layer separation, or analyzing transitive import paths. Do NOT use for tracing raw usages of a symbol (use gograph_usages instead). COMPLETENESS: Requires 'package' parameter. Returns a structured package list showing direct or full transitive dependency chains. Example package: 'internal/search'.

gograph_embedsA

Identify and list all parent structures that compositionally embed the specified target struct. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when analyzing struct nesting, identifying compositions, or tracing where shared types are embedded. Do NOT use if you are looking for interfaces implemented (use gograph_implementers instead). COMPLETENESS: Requires 'struct' parameter. Returns a detailed array of embedding parent structs and their file definitions. Example struct: 'Symbol'.

gograph_endpointA

Audit and analyze HTTP route endpoints, handlers, and anonymous closure bodies. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to review HTTP interface definitions, verify request flow bindings, or audit handler implementations. Do NOT use for internal Go functions (use gograph_source instead). COMPLETENESS: Returns HTTP methods, paths, handler signatures, and handler bodies. Example package: 'cmd/gograph'.

gograph_envsA

Extract and audit all environment variables (os.Getenv, os.LookupEnv) referenced across the codebase. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when compiling configuration profiles, verifying env parameter bindings, or auditing configuration management. Do NOT use for magic constant literals (use gograph_literals instead). COMPLETENESS: Returns a structured list of env keys, their default fallbacks, and the file and line locations of the call.

gograph_errorflowA

Trace the flow and propagation of returned errors from a specific origin function. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when auditing error-handling completeness, locating unhandled errors, or tracing failure modes. Do NOT use for standard call graphs (use gograph_callers/callees instead). COMPLETENESS: Requires 'function' parameter. Returns error bubbling paths up the call chain. Example function: 'BuildGraph'.

gograph_errorsA

Locate all explicit error creation points (errors.New, fmt.Errorf, sentinel definitions) inside the codebase. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when auditing error taxonomies, cataloging error codes, or standardizing error handling. Do NOT use to trace propagation paths (use gograph_errorflow instead). COMPLETENESS: Returns a structured checklist of all matched error creation spots, showing their file and line coordinates.

gograph_explainA

Generate high-fidelity explanations, downstream impacts, and documentation summaries for codebase symbols. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to construct technical documentation, onboard to complex implementations, or summarize logic for PRs. Do NOT use for line-by-line raw source code (use gograph_source instead). COMPLETENESS: Requires 'symbol' parameter. Returns a detailed semantic summary of the symbol's role, dependencies, and calls. Example symbol: 'BuildGraph'.

gograph_fieldsA

Extract all fields, types, and struct tags declared inside a specific Go struct. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when inspecting struct definitions, verifying struct layouts, mapping JSON/database tags, or generating serialization logic. Do NOT use if you are looking for struct methods (use gograph_node or gograph_source instead). COMPLETENESS: Requires 'struct' parameter. Returns field names, Go types, and exact struct tag string metadata, providing full visibility into struct fields without manual code viewing. Example struct: 'Graph'.

gograph_fixturesA

Locate and audit external data files, JSON payloads, or database seeds used inside test suites. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to trace test dependencies or catalog test datasets. Do NOT use for active test functions (use gograph_tests instead). COMPLETENESS: Returns a structured checklist of all referenced testing datasets and their file paths.

gograph_focusA

Extract targeted call-graph and dependency context for a single Go package. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when you need to understand the architecture, files, internal calls, and dependencies of a specific package directory before making edits. Do NOT use for global searches (use gograph_query instead). COMPLETENESS: Requires 'package' parameter. Returns a detailed listing of all files, defined symbols, calls, and internal dependencies within the target package. Example package: 'internal/search'.

gograph_globalsA

Audit all global variable declarations, shared package states, and constants defined inside the repository. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to discover mutable global state, check config values, or identify thread-safety hazards. Do NOT use for local scope variables. COMPLETENESS: Returns a structured checklist of all global variables, constants, package paths, and types.

gograph_godobjA

Detect God Object code smells by analyzing structural sizes, method counts, and references. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when auditing architectural modularity or identifying monolithic structs that should be refactored. Do NOT use for general struct layout checks (use gograph_fields instead). COMPLETENESS: Returns concrete structs exceeding target field or method count limits.

gograph_hotspotA

Locate code hotspots by combining structural call complexity and incoming dependency metrics. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when conducting performance audits, locating architectural coupling hotspots, or planning structural simplification. Do NOT use for single-package metrics (use gograph_focus instead). COMPLETENESS: Returns a prioritized list of hotspot packages, complexity counts, and caller metrics.

gograph_impactA

Traverse the call graph backwards to find all symbols that eventually call the target (blast radius). BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to determine the blast radius of a sensitive core component before refactoring. Do NOT use for direct callers only (use gograph_callers instead). COMPLETENESS: Supports single symbol, uncommitted changes, or since a git ref. Returns a transitive list of all upstream affected symbols. Example symbol: 'BuildGraph'.

gograph_implementersA

Find all structs in the codebase that implement the specified interface via Go duck-typing. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when tracing polymorphism, identifying dependency injection structures, or locating mock implementations. Do NOT use if you are looking for struct fields (use gograph_fields instead). COMPLETENESS: Requires 'interface' parameter. Returns a detailed list of implementing concrete structs and their package file locations. Example interface: 'error'.

gograph_importsA

Find all files and packages that import a specific internal or third-party package. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when mapping package dependency relationships, isolating features, or tracing where third-party libraries are used. Do NOT use if you need a package's own imports (use gograph_deps instead). COMPLETENESS: Requires 'package' parameter. Returns a complete array of file paths and importing packages referencing the target import path. Example package: 'golang.org/x/tools'.

gograph_interfacesA

Audit and list all Go interface declarations, complete with their defined method signatures. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when mapping API abstractions, checking interface contracts, or reviewing modular design patterns. Do NOT use to find implementers (use gograph_implementers instead). COMPLETENESS: Returns all interface names, method signatures, package paths, and file locations.

gograph_literalsA

Find all primitive literals (strings, integers, floats, booleans) matching a filter pattern. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to identify hardcoded magic values, config strings, or credentials. Do NOT use for raw database queries (use gograph_sql instead). COMPLETENESS: Optional 'type' filter (string/int). Returns a list of matched literals and their code positions. Example pattern: 'mcp'.

gograph_mocksA

Identify and locate all test mocks, double definitions, and test-only helper structs. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to identify active mock wrappers or find test fixtures. Do NOT use for production interface implementers (use gograph_implementers instead). COMPLETENESS: Requires 'interface' parameter. Returns test/mock concrete structs implementing the specified interface. Example interface: 'error'.

gograph_mutateA

Trace and audit all state-mutation and assignment points where a specific struct field gets modified. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when diagnosing state bugs, checking data mutability, or analyzing struct field lifetimes. Do NOT use for direct struct layouts (use gograph_fields instead). COMPLETENESS: Requires 'struct' and 'field' parameters. Returns file and line locations where the target field is assigned or updated. Example struct: 'Symbol', example field: 'Name'.

gograph_nodeA

Extract full AST property details for any specific symbol, package, or file node in the repository graph. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when you need deep structural metadata including kinds, signatures, documentation, or exact file lines. Do NOT use if you need raw source code only (use gograph_source instead). COMPLETENESS: Requires 'name' parameter. Returns complete node properties and fields. Example name: 'Graph'.

gograph_orphansA

Find functions and methods that are unreachable from any entry point (main, HTTP routes, exported symbols). BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when clean-up is needed or to locate dead code that should be purged from the repository. Do NOT use for checking specific symbol usages (use gograph_usages instead). COMPLETENESS: Returns a list of orphan symbols, their packages, and file definitions.

gograph_pathA

Trace and find the direct or transitive call paths connecting a starting source symbol to a target destination symbol. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when tracing synchronous control flow, debugging deadlocks, or mapping execution paths. Do NOT use if you only need direct callers (use gograph_callers instead). COMPLETENESS: Requires 'from' and 'to' parameters. Returns call chains connecting the two symbols. Example from: 'Serve', example to: 'BuildGraph'.

gograph_planA

Analyze structural changes and dependencies to output a detailed refactoring execution plan. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool before making complex multi-file architectural changes or package refactoring. Do NOT use for trivial single-file edits. COMPLETENESS: Returns a step-by-step refactoring workflow detailing symbol modifications, dependency steps, and testing verification checklists.

gograph_publicA

Extract all public, exported symbols across the entire repository, categorized by package. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when building a high-level catalog of system services or creating integration boundaries. Do NOT use if you need internal private details (use gograph_node instead). COMPLETENESS: Returns a structured outline of all exported functions, structs, interfaces, and variables.

gograph_queryA

Search the Go repository for symbols, packages, files, or imports using a keyword term. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool during the initial exploration phase when you have a keyword or feature name but do not know which files or packages contain the relevant code. Do NOT use if you already know the exact symbol name (use gograph_source or gograph_node instead). COMPLETENESS: Returns a structured list of matching symbols, files, and imports, along with their location and kind. Example: 'Graph', 'Serve'.

gograph_returnusageA

Verify the patterns and coverage of return parameter usages and validation handling. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to check if returned parameters are properly inspected, validated, or captured after method invocations. Do NOT use for error flow bubbling (use gograph_errorflow instead). COMPLETENESS: Returns matched call locations and variable binding status.

gograph_reviewA

Run an architectural consistency and design constraint review against defined code boundaries or specific symbols. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool during post-edit verification, CI pipelines, or refactoring phases to ensure new additions do not violate boundary limits. Do NOT use for general dependency tree listing (use gograph_deps instead). COMPLETENESS: Requires either 'symbol' or 'uncommitted' set to true. Returns a structured checklist of all rules evaluated, listing exact package paths and files violating architectural boundaries. Example symbol: 'Graph'.

gograph_routesA

Discover all registered HTTP routes and endpoints defined inside the codebase. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to map out the entire web API structure of a microservice or application. Do NOT use if you need downstream call details (use gograph_endpoint instead). COMPLETENESS: Returns a structured table of HTTP method/route paths mapped to Go handlers.

gograph_schemaA

Locate Go structs that map to a specific database table or schema using struct tags like db or gorm. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when mapping ORM structures, tracing database model boundaries, or locating table schemas. Do NOT use for non-ORM Go structs (use gograph_fields instead). COMPLETENESS: Requires 'table' parameter. Returns concrete structs mapping to the specified table. Example table: 'users'.

gograph_skeletonA

Generate high-level skeletal outline structural abstractions of codebase files, excluding implementation details. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when you need to understand the skeleton structure of files quickly without reading massive line counts. Do NOT use if you need full function implementations (use gograph_source instead). COMPLETENESS: Returns a concise abstract list of struct schemas, function definitions, and interfaces.

gograph_sourceA

Extract the exact Go source code body for a specific function, method, struct, or interface. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when you need to read the implementation details of a specific symbol without loading large files. Do NOT use if you need call hierarchies (use gograph_callers/gograph_callees instead). COMPLETENESS: Requires 'symbol' parameter. Returns the exact block of source code defining the target symbol, complete with line numbers. Example symbol: 'BuildGraph'.

gograph_sqlA

Extract and analyze all raw SQL query literals, database touches, and transaction blocks inside the codebase. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when auditing database interactions, debugging database performance, or reviewing raw queries. Optional filter by keyword. Do NOT use for Go structs mapped to database tables (use gograph_schema instead). COMPLETENESS: Returns a list of matching SQL statements, their file and line locations, and the parent Go functions containing the database touch. Example term: 'SELECT'.

gograph_staleA

List all Go package dependencies that are currently stale and require rebuilding. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when verifying incremental build status, caching layers, or validating compilation health. Do NOT use if package dependencies are up to date. COMPLETENESS: Returns a list of stale package paths.

gograph_statsA

Generate comprehensive repository-level code statistics including total package counts, symbol frequencies, and imports. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to build high-level code density reports, trace total codebase sizes, or verify initial repository parsing health. Do NOT use for single symbol profiling (use gograph_node instead). COMPLETENESS: Returns total counts of files, lines, packages, structs, functions, and interfaces.

gograph_testsA

Find all unit tests, benchmark functions, and testing suites declared in Go test files. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool to identify existing test coverage or locate specific verification flows before running tests. Do NOT use for production code symbols (use gograph_node instead). COMPLETENESS: Returns test functions, target packages, and their file definitions.

gograph_usagesA

Find all references and semantic usages of a specific function, struct, or variable across the codebase. BEHAVIOR & SAFETY: This is a 100% local, read-only static analysis tool. It has no side effects, requires no authorization or credentials, has no rate limits, and performs zero destructive modifications. USAGE GUIDELINES: Call this tool when renaming symbols, checking references, or identifying dead code usages. Do NOT use for AST metadata only (use gograph_node instead). COMPLETENESS: Requires 'symbol' parameter. Returns files and exact line locations containing references to the target symbol. Example symbol: 'BuildGraph'.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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/ozgurcd/gograph'

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