Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
codetopo_indexC

Index a repository into a codetopo graph database.

codetopo_descendantsB

Nodes transitively reachable from a node over calls and imports edges.

codetopo_ancestorsA

Nodes from which a node is transitively reachable over calls and imports edges.

codetopo_blast_radiusB

Nodes that break if a node changes: dependents, overriders, and implementers.

codetopo_pathB

Shortest typed path between two nodes, or the reason there is none.

codetopo_statsA

Node and edge totals for an index, with per-kind breakdowns.

codetopo_verifyB

Verify the tamper-evident audit chain of an index.

codetopo_snapshotB

Export the whole graph as a portable snapshot, bound to the audit head.

codetopo_neighborhoodB

The subgraph within a few hops of a node, in both directions (contains/defines excluded).

codetopo_get_symbolA

One node in full: kind, location, tier, defines and refs. Errors when the id is unknown.

codetopo_search_symbolsA

Find symbols by name (case-insensitive substring of the label) - the discovery step before the exact-id queries.

codetopo_describe_schemaA

The schema this server speaks: node and edge kinds, tier rules, and the query vocabulary. Needs no database.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 12 tools

Disambiguation4/5

Most tools target clearly distinct operations: indexing, traversal in one direction, blast-radius calculation, pathfinding, symbol lookup, schema description, export, and audit verification. The main potential confusion is between traversal tools like descendants, ancestors, neighborhood, and blast_radius, since all involve following graph edges, but the descriptions provide enough detail to distinguish their specific semantics.

Naming Consistency4/5

All tool names use a consistent codetopo_ prefix and snake_case formatting, which makes them easy to scan. The naming mixes noun-style names (descendants, ancestors, path, stats, neighborhood) with verb-style and verb_noun names (index, verify, snapshot, get_symbol, search_symbols, describe_schema), but the pattern remains predictable and readable.

Tool Count5/5

Twelve tools is a well-scoped set for a code graph database server, covering indexing, several complementary graph queries, schema introspection, snapshot export, and audit verification. Each tool appears to earn its place without obvious redundancy or filler.

Completeness4/5

The surface covers the core lifecycle: creating an index, discovering and inspecting symbols, traversing relationships, pathfinding, blast-radius analysis, schema description, export, and audit verification. Minor gaps might include listing or deleting existing indexes, but the read/query side is strongly covered for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessWithin a week