Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ATTOCODE_API_KEYNoSet in the agent's environment when connecting to a self-hosted remote/team server. Use the `intelligence:read` scope for analysis and add `intelligence:write` for knowledge changes. Not needed for local working-tree analysis.

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
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
notify_file_changedA

Tell the server which files changed, so that the index and search read the new content.

A server that watches the project finds edits without this call.

Args: files: Changed file paths, relative or absolute.

impact_analysisA

List the files that a change to the given files can affect: the files that import them, directly or through other files.

cross_referencesA

Find where a symbol is defined and each place that references it: calls, imports and attribute accesses.

Args: file_path: When names collide, select the definition in this repository-relative file. line: Select the definition by its start line. cursor: Continue a paged result. page_size: References per page, 1 to 100 (default 20).

call_graphB

Follow the calls of a function or method.

Args: symbol: Function or method name, qualified or bare. direction: "callees" (what it calls) or "callers" (what calls it). depth: Maximum number of hops (default 1).

dependenciesC

Show what a file imports and which files import it.

symbolsB

List the functions, classes and methods that a file defines.

search_symbolsB

Find symbol definitions by name, best match first: exact, prefix, substring, case-insensitive and camelCase or snake_case parts.

Args: name: A name or part of one, for example "parse_file" or "Router". kind: Optional filter: function, class, method, variable, constant, interface or type. task_hint: Optional task text that orders equal matches.

inspect_symbolA

Get a symbol in one call: definition, source excerpt, references, imports and candidate tests.

A name is enough. For an ambiguous name, the result lists choices: give the repository-relative file_path and the definition start line to select one. Add task_hint to order the excerpts and tests for your task. For a long definition, follow next_source or set source_start_line. Keep each context_ranges group with its excerpt. Missing relationships do not prove absence.

explore_codebaseB

List one directory level: subdirectories with file counts and languages, and files with importance and top symbols.

Args: path: Directory relative to the project root ("" for the root). importance_threshold: Minimum file importance, 0.0 to 1.0. task_hint: Optional task text that orders the files.

project_summaryB

Summarize the project: purpose, size, entry points, architecture, layout, dependency layers, tech stack, tests and build.

bootstrapB

Find where a behavior is implemented in an unfamiliar repository.

With task_hint, the result has the code that matches the task, a project summary, a map and the conventions.

Args: task_hint: What you want to find or change. indexing_depth: "auto" (default), "eager", "lazy" or "minimal".

relevant_contextB

Show the files around the given files: what they import and what imports them, with their top symbols.

Args: files: Center file paths. depth: Number of hops, 1 or 2 (default 1). task_hint: Optional task text that orders the files.

review_changeB

Review changed files for security issues, rule violations and convention problems in one report.

Args: files: Files to review (default: the files that git reports as changed). mode: "quick" (security only) or "full".

suggest_testsB

Suggest candidate tests using imports and syntax; optionally focus on a symbol and task.

semantic_searchA

Search the code by meaning with a natural-language query. Returns files, functions and classes, best first.

Args: query: For example "authentication middleware". file_filter: Optional glob, for example "*.py". branch: Remote service only. Local search reads the working tree. mode: "auto" (default), "keyword", or "vector" (waits for embeddings).

fast_searchA

Search file contents with a regular expression. A trigram index selects the candidate files first.

Args: pattern: A regular expression, for example "def process_.*event". path: Optional subdirectory relative to the project root. selectivity_threshold: Skip the index when more than this share of files can match (default 0.10). explain: Add search diagnostics to the output.

capabilitiesC

Available tools, profiles, workspace selection, and optional enhancements.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Agent guidelines

TDQS

B3.2/5.0

Scored across 17 tools

Disambiguation4/5

Most tools have a distinct angle: symbol-name search (search_symbols), regex content search (fast_search) and meaning search (semantic_search) are clearly separated, as are call_graph and cross_references. There is real overlap among the neighborhood/context tools (dependencies, impact_analysis, relevant_context, explore_codebase) and between the bundle tool inspect_symbol and the specialized reference/test tools, but descriptions give enough cues to choose correctly in most cases.

Naming Consistency4/5

All names are snake_case with no style mixing, which makes the set readable. However the conventions are blended: some are verb_object (search_symbols, inspect_symbol, review_change, suggest_tests, notify_file_changed) while others are bare noun phrases (symbols, dependencies, capabilities, project_summary, call_graph), a minor inconsistency rather than a usability problem.

Tool Count4/5

At 17 tools the server is slightly above the comfortable range, but each tool maps to a real code-intelligence capability (search, symbols, graphs, context, review, tests). A few could be folded together—bootstrap overlaps project_summary/explore_codebase, and inspect_symbol duplicates parts of cross_references and suggest_tests—so the surface is a touch heavier than necessary.

Completeness4/5

Coverage is broad for a code-intelligence domain: three search modes, symbol definition/reference lookup, call graph, dependency and impact analysis, contextual exploration, review and test suggestion, plus index notification and a capabilities tool. Minor gaps remain—no explicit file-content read or manual re-index/status tool, and no symbol-level write operations—but these are largely outside the stated read-oriented purpose.

Maintenance

ActivityActive
ResponsivenessNo issues