Skip to main content
Glama
ganievs
by ganievs

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TODOIST_API_TOKENYesYour Todoist API token

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
add_taskB

Create a TODO task

update_taskC

Update a TODO task

get_taskC

Get a TODO task

list_tasksB

List and filter TODO tasks

close_taskC

Close a TODO task

reopen_taskB

Reopen a TODO task

delete_taskB

Delete a TODO task

add_projectB

Create a new Todoist project

get_projectC

Get details of a Todoist project

list_projectsC

List all Todoist projects

update_projectC

Update an existing Todoist project

delete_projectC

Delete a Todoist project

get_project_collaboratorsC

Get collaborators for a Todoist project

add_sectionB

Create a new section in a Todoist project

get_sectionB

Get details of a Todoist section

list_sectionsB

List all sections in a Todoist project

update_sectionB

Update an existing Todoist section

delete_sectionC

Delete a Todoist section

add_labelD

Create a label

get_labelB

Get a label

list_labelsC

List and filter labels

delete_labelC

Delete a label

add_commentC

Add a comment to a task

update_commentC

Update a comment

get_commentC

Get a comment

list_commentsC

List and filter comments

delete_commentC

Delete a comment

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.1/5.0

Scored across 27 tools

Disambiguation5/5

Each tool targets a distinct resource and action. There is no overlap in purpose; for example, add_task and add_project operate on different resources, and get_task vs list_tasks are clearly separated.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., add_task, delete_comment, list_projects). The verbs and nouns are standardized, making it easy to predict the naming for any missing operation.

Tool Count4/5

27 tools is on the higher end but appropriate given the number of resource types (task, project, section, label, comment) with full CRUD plus extras like close/reopen and collaborators. It could potentially be trimmed but is still well-scoped.

Completeness4/5

The set covers all major CRUD lifecycle for tasks, projects, sections, labels, and comments, plus close/reopen for tasks. Minor gaps exist (e.g., no move_task or assign_task) but the core workflows are complete.

Maintenance

ActivityInactive
ResponsivenessNo issues