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

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
app-statusD–
get-areasD–
get-tagsD–
get-projectsD–
get-headingsD–
suggest-headingsD–
validate-headingsD–
get-todosD–
get-inboxD–
get-todayD–
get-upcomingD–
get-anytimeD–
get-somedayD–
get-logbookD–
get-trashD–
get-tagged-itemsD–
get-recentD–
search-todosD–
search-itemsD–
search-advancedD–
get-project-structureD–
suggest-task-placementD–
summarize-projectD–
versionD–
show-quick-entryD–
log-completedD–
empty-trashD–
add-todoD–
create-project-with-headingsD–
add-projectD–
updateD–
update-projectD–
showD–
show-itemD–
searchD–
jsonD–
update-todoD–

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

D1.5/5.0

Scored across 37 tools

Disambiguation2/5

Multiple tools have unclear boundaries and overlapping purposes, such as search/search-advanced/search-items/search-todos and show/show-item, which could cause confusion and misselection. While some tools like get-inbox and get-today have distinct purposes, the significant overlap in search and display functions creates ambiguity.

Naming Consistency3/5

The naming follows a mostly consistent verb-noun pattern with hyphens (e.g., get-projects, update-todo), but there are deviations like json, version, and show without clear nouns, and inconsistencies such as add-project vs create-project-with-headings. The pattern is readable but mixed in style.

Tool Count2/5

With 37 tools, the count is too high for the apparent task management domain, suggesting bloat and potential redundancy, as seen with multiple search and get variants. This many tools can overwhelm agents and indicate poor scoping, though it's not extreme like 50+.

Completeness4/5

Inferred as a task/project management system, the tool set covers core CRUD operations (add, get, update, delete via trash), lifecycle aspects (log-completed, summarize-project), and advanced features like search and suggestions, with only minor gaps such as potential missing bulk operations or detailed configuration tools.

Maintenance

ActivityInactive
ResponsivenessNo issues