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
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
find_referencesB

Callers, importers and references of one entity. Chains? trace_data_flow.

get_context_packC

Bodies, signatures and routes around entities or a question, in one bundle.

get_entity_sourceC

One entity's exact source, by id.

graph_neighborhoodB

What one entity depends on and what depends on it. Paths: trace_data_flow.

impact_analysisC

Every entity a change could affect, from entity_ids or change_ids.

kin_graph_statusC

Graph and embedding counts. last_settled_selected_graph marks a last settled reading.

kin_initA

Set a folder up as a Kin repository when it is not one.

kin_mutateB

Commit targeted entity changes atomically, in one call.

kin_provenance_queryB

Who changed an entity, when, and whether it was approved.

kin_session_endB

Session plumbing for writes. Close an open session.

kin_session_execB

Build, test or run this project with its toolchain. Session needs can_execute.

kin_session_heartbeatB

Session plumbing for writes. Keep a session alive.

kin_session_startB

Session plumbing for writes. Open one; get a session_id.

kin_transaction_abortA

Transaction plumbing for writes. Discard what is staged and close it.

kin_transaction_beginA

Transaction plumbing for writes. Open one; get a transaction_id.

kin_transaction_commitB

Transaction plumbing for writes. Publish everything staged, atomically.

kin_transaction_stageC

Transaction plumbing for writes. Stage an update, create, delete or rename.

lexical_lookupB

Exact literals, punctuation included, in stored graph fields. Lexical evidence only.

semantic_locateA

Find code by describing what it does. Know the exact name? semantic_search.

semantic_searchC

Declarations by name, kind or language. By meaning? semantic_locate.

trace_data_flowA

The ordered call chain out from one entity. Two endpoints? trace_path.

trace_pathA

How one entity reaches another, as hops. One endpoint? trace_data_flow.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 22 tools

Disambiguation4/5

Tools cover distinct retrieval modes (lexical, semantic by name vs. meaning, trace flow vs. path, references vs. neighborhood) and descriptions explicitly cross-reference to guide selection. Some overlap remains among graph query tools and between kin_mutate and transaction staging, but boundaries are mostly clear.

Naming Consistency3/5

All names are snake_case, but prefixes and patterns are mixed: kin_* appears on session/transaction/init/mutate/status/provenance tools, while query tools use bare verb_noun or noun_noun forms. The set is readable but not fully consistent.

Tool Count3/5

22 tools is borderline heavy for a code-graph server. The scope spans read queries, write/session/transaction plumbing, provenance, init, and execution, so most tools earn their place, but the count is on the high side.

Completeness4/5

The surface covers graph querying, entity mutation with transaction support, sessions, provenance, initialization, execution, and direct source retrieval. Minor gaps like bulk entity listing or file-level operations exist, but core lifecycle appears complete.

Maintenance

ActivityActive
ResponsivenessUnresponsive