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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
log_conversationA

记录AI对话 - 所有会话都要记录

使用规范: • userRequest: 用户原始需求+上传文件说明 • aiTodoList: 你的执行计划清单(即使只是查看也要列出) • aiSummary: 你的操作总结(3-5句话,包括解释、分析等) • fileOperations: 文件操作总结,格式:"动作 文件路径 - 说明"(可为空) • title: 对话标题(可选) • tags: 标签数组(可选)

search_conversationsC

搜索历史对话记录

支持: • 关键词搜索 • 文件名模式搜索 • 时间范围筛选 • 标签过滤

get_context_suggestionsC

获取相关上下文建议

基于当前输入和文件推荐历史记录

list_projectsC

List all projects with optional statistics

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 4 tools

Disambiguation4/5

The four tools have distinct purposes: get_context_suggestions provides recommendations, list_projects enumerates projects, log_conversation records conversations, and search_conversations finds historical data. There is minor potential confusion between get_context_suggestions and search_conversations, as both involve retrieving conversation-related information, but their descriptions clarify that one is for recommendations and the other for direct searches.

Naming Consistency3/5

The tool names follow a mixed pattern: get_context_suggestions and search_conversations use verb_noun format, while list_projects and log_conversation use verb_noun but with slight inconsistency in structure. The naming is readable but lacks strict uniformity, as seen in the variation between 'get_' and 'search_' prefixes and the absence of a consistent convention across all tools.

Tool Count4/5

With 4 tools, the count is appropriate for a conversation logging server, covering core functions like listing, logging, searching, and context suggestions. It is slightly lean but reasonable, as each tool serves a distinct role without obvious redundancy or bloat, though it might benefit from additional tools for advanced management tasks.

Completeness4/5

The tool set covers essential CRUD-like operations for conversation logging: list_projects for reading, log_conversation for creating, and search_conversations for querying, with get_context_suggestions adding utility. Minor gaps exist, such as the lack of update or delete tools for conversations or projects, but agents can likely work around these limitations for basic logging workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues