Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_user_settings_get

Retrieve user settings for reminder preferences, notification settings, sounds, and theme configuration.

Instructions

Get user settings including reminder preferences, notification settings, sounds, and theme configuration.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "todoist_user_settings_get"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.3

TDQS

A3.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description only states the tool gets settings, implying read-only behavior, but does not disclose any behavioral traits beyond what is obvious from the name. With no annotations, the description does not address permissions, rate limits, or potential side effects (though likely none). It adds minimal value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 12 words, efficiently conveying the tool's purpose. It is well-structured and front-loaded. However, it could be slightly more informative without losing conciseness, e.g., by mentioning the output format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has no parameters and no output schema, the description covers the essential purpose. It lists categories of settings, which helps the agent understand the scope. However, it does not specify that the tool is read-only or that it returns JSON, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so baseline is 4. The description accurately reflects that no parameters are needed and lists the settings covered, providing context that the schema itself cannot convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves user settings and lists specific categories (reminder preferences, notifications, sounds, theme). This distinguishes it from sibling tools like 'todoist_user_get' which likely retrieves user profile information.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusion criteria relative to sibling tools such as 'todoist_user_get' or other configuration-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools