Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOCINTEL_DATANoWhere extraction results are stored..data/results
DOCINTEL_INBOXNoFolder the tools may read documents from.samples
DOCINTEL_AUDIT_LOGNoAudit trail, one JSON line per tool call..data/audit.jsonl

Instructions

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

Extracts structured data from insurance documents (certificates of insurance and loss runs). Call list_documents to see what is available, extract_document to process one, and list_low_confidence_fields to see what a human still needs to review. Extraction results with status 'needs_review' or 'rejected' must not be treated as final.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

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

Tools

Functions exposed to the LLM to take actions

NameDescription
list_documentsA

List the names of documents available for extraction.

extract_documentB

Extract structured data from one document and store the result.

Returns the document id, detected type, status (accepted, needs_review or
rejected), the normalized data, and any validation issues.
get_extractionA

Fetch a stored extraction result, including per-field confidence, by document id.

list_low_confidence_fieldsC

List the fields of a stored extraction that need human review, and why.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.3/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a distinct action+target: listing documents, running an extraction, fetching a stored result, and listing low-confidence fields. The only mild overlap is between get_extraction and list_low_confidence_fields, since both read extraction results, but the descriptions make the split (full result vs. review-needed fields) reasonably clear.

Naming Consistency5/5

All four names follow a clean snake_case verb_noun pattern (list_documents, extract_document, get_extraction, list_low_confidence_fields). Verb choice is meaningful: list for enumeration, extract for the write action, get for single-item fetch.

Tool Count4/5

Four tools is a coherent, small surface for a focused extraction service, and each one plays a role in the extract-then-review flow. It sits slightly on the thin side given the workflow it implies, but nothing here is redundant.

Completeness3/5

The surface covers listing documents, extracting, and reading results, but the human-review loop is a dead end: you can list low-confidence fields yet there is no tool to submit corrections, accept/reject an extraction, or re-run one. No delete, update, or batch extraction operations are exposed, which will limit agents working beyond the happy path.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues