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
handoff_readA

A one-call overview of files or folders, in a fixed format with real line numbers. For one specific question, your own search and partial reads are usually cheaper. Code does the work, with no model: a named identifier or quoted string gets the matching lines; source code gets an outline (definitions, docstrings, constants); logs get a profile (each kind of line with counts, odd values, first big jump, rare lines in full); JSON and CSV get their shape. Plain text goes to the local model only if the user turned that on. The first line says which tool ran. Every line number is real: Read the lines that matter before acting on them.

handoff_profileA

Summarize log files by counting, with no model, so you do not read them into your own context. Each kind of line is shown once with its count, first and last line, and the spread of its values (with any odd one out and the first big jump in a number); lines that happen only a few times are listed in full. Line numbers are real: Read the lines that matter before acting on them.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.8/5.0

Scored across 2 tools

Disambiguation3/5

handoff_read is a broad catch-all that already promises log profiling ('logs get a profile: each kind of line with counts, odd values, first big jump, rare lines in full'), which is essentially the whole of handoff_profile. The descriptions hint that profile is the specialized log path, but an agent holding a .log file could reasonably pick either, and the overlap is substantial rather than incidental.

Naming Consistency4/5

Both tools share a clear 'handoff_' namespace prefix followed by a single action word, so the pattern is predictable and readable. The only minor wrinkle is that 'profile' reads as both noun and verb, but the convention is still consistent across the pair.

Tool Count3/5

Two tools is thin even for a deliberately narrow, context-saving server, and one of the two largely duplicates capabilities already claimed by the other. A small surface is defensible here, but it sits at the borderline rather than feeling well-scoped.

Completeness3/5

The domain is cheap, model-free inspection of files, code, logs, JSON and CSV, and that is covered for the 'overview' case, with the description even telling agents to fall back to their own Read/search for targeted questions. However, there is no tool for targeted extraction, directory listing, or producing an actual handoff artifact, so the lifecycle stops short of what the server name implies.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues