Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CHOPPER_SNAPNosentence (default), word or nonesentence
CHOPPER_DEVICENoauto, cpu or cudaauto
CHOPPER_VARIANTNobase (default), small, base-pl or small-plbase

Instructions

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

Chopper cuts exact quotes that answer a question out of long retrieved text (2-5% of it is typically kept). Call it BEFORE reading many search results, documents or files in full: pass the user's question and the raw text, then read the returned quotes instead of the whole text. Quotes are verbatim, with their source and character offsets. decision == 'SEARCH' means the text most likely does not contain the answer: search again or retrieve other documents rather than answering from it. The same call ranks the passages by relevance (ranking), so no separate reranker is needed; use rank_passages when whole passages, not quotes, are wanted.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
chop_passagesA

Cut the exact quotes that answer question out of passages (retrieved snippets, search results, tool outputs). Returns the quotes (verbatim, with passage number and character offsets), a ready-to-read context string, and decision ANSWER (the passages hold the answer) or SEARCH (search again).

rank_passagesB

Rank passages by relevance to question (the chopper used as a reranker: on a held-out 8-language set it ranks within ~1 nDCG point of bge-reranker-v2-m3 at the same speed). Returns the top_k passages, most relevant first, with their index and relevance (0..1), plus decision ANSWER / SEARCH.

chop_filesA

Read local text files (notes, docs, logs, code, exported pages), split them into ~1,000-character passages and cut out the exact quotes that answer question. Each quote carries its file path and character offset in that file. Use it instead of reading long files in full when only part of them is relevant.

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 3 tools

Disambiguation4/5

rank_passages is clearly distinct, and chop_passages vs chop_files differ by input source. However, the two chop tools share the same core extraction behavior and return shape, so an agent could briefly hesitate between them when file-derived snippets are involved.

Naming Consistency5/5

All names use consistent snake_case verb_noun form: chop_passages, rank_passages, chop_files. The shared chop_ prefix accurately groups related operations without introducing inconsistent conventions.

Tool Count5/5

Three tools is a tight, well-scoped surface for a quote-extraction/reranking utility. Each tool covers a distinct input mode or operation, with no filler tools.

Completeness5/5

The surface covers both core inputs (provided passages and local files) plus reranking, and returns decisions that guide next steps. No obvious operation is missing for the stated chopper/reranker domain.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues