Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
API_BINDNoAPI server bind address127.0.0.1
API_PORTNoWeb API server port5174
MODEL_IDNoHugging Face model for embeddingsXenova/all-MiniLM-L6-v2
NODE_ENVNoEnvironment modedevelopment
WATCH_DIRNoDirectory to watch for file changes
CHUNK_SIZENoTarget chunk size in characters1000
SQLITE_PATHNoPath to SQLite database file./data/index.db
DEBUG_DOTENVNoEnable dotenv debug outputfalse
CHUNK_OVERLAPNoOverlap between chunks in characters120
VERBOSE_LOGGINGNoEnable detailed logsfalse

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
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchB

Search for similar content using semantic search

upsert_documentsC

Insert or update documents with text content

delete_documentsC

Delete documents by ID or external ID

list_documentsC

List all documents with pagination

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: delete_documents removes documents, list_documents retrieves them, search finds similar content, and upsert_documents inserts or updates. An agent can easily tell them apart based on their specific actions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., delete_documents, list_documents, upsert_documents), with 'search' as a slight deviation that still fits semantically. The naming is predictable and readable throughout.

Tool Count5/5

With 4 tools, the server is well-scoped for document management, covering core operations like listing, searching, upserting, and deleting. Each tool earns its place without being too sparse or bloated.

Completeness4/5

The tool set provides strong coverage for basic document CRUD and search operations, but lacks explicit tools for actions like retrieving a single document by ID or updating metadata, which could be minor gaps agents might need to work around.

Maintenance

ActivityInactive
ResponsivenessNo issues