Skip to main content
Glama
istefox

istefox-dt-mcp

Official
by istefox

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ISTEFOX_RAG_MODELNoOverride the embedding model (e.g. BAAI/bge-m3). Only used when RAG is enabled.paraphrase-multilingual-MiniLM-L12-v2
ISTEFOX_RAG_ENABLEDNoIf truthy: enables the vector RAG provider.false
ISTEFOX_PREVIEW_TTL_SNoOverride TTL in seconds for preview_token (default 5 minutes). Valid range: 1–3600.300
ISTEFOX_WEBHOOK_TOKENNoOptional token for RAG webhook sync.
ISTEFOX_FAST_LIST_DATABASESNoIf truthy (1/true/yes/on): list_databases skips computing record_count (returns null). Useful on large databases.false

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": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_databasesD
searchD
find_relatedD
ask_databaseD
file_documentD
bulk_applyD
summarize_topicD

Prompts

Interactive templates invoked by user choice

NameDescription
weekly_reviewGuida una review settimanale dei documenti DEVONthink recenti.
triage_inboxGuida il triage dell'Inbox DEVONthink con file_document in dry-run.

Resources

Contextual data attached and managed by the client

NameDescription
dt-databasesOpen DEVONthink databases visible to the caller (consent-filtered). Deterministic, bounded, read-only.

TDQS

D1.6/5.0

Scored across 7 tools

Disambiguation2/5

Multiple tools appear to overlap in purpose, such as 'search', 'find_related', and 'ask_database', which all seem to query data in some form. Without descriptions, an agent would struggle to differentiate these, leading to potential misselection. 'file_document' and 'bulk_apply' are also vague and could be interpreted in multiple ways.

Naming Consistency3/5

All tool names use snake_case and mostly follow a verb_noun pattern (list_databases, find_related, summarize_topic), but the verbs themselves are inconsistent, mixing generic actions like 'search' and 'ask' with more specific ones. This creates a somewhat readable but not fully predictable naming scheme.

Tool Count5/5

With 7 tools, the server is well within the ideal 3-15 range for a focused utility. Each tool seems to cover a distinct (if overlapping) aspect of data interaction, and the count is neither thin nor bloated.

Completeness2/5

The tool surface lacks clear lifecycle coverage for any specific resource. There is list and search functionality, but no obvious create, update, or delete operations for databases or documents, making the server feel like a partial toolkit. The domain itself is ambiguous, so it is unclear what the intended complete workflow would be.

Maintenance

ActivityInactive
ResponsivenessSyncing