Skip to main content
Glama
Sign In
Todoist MCP Server

Todoist MCP Server

by greirson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

todoist_test_all_features

Run comprehensive tests to verify all Todoist MCP features. Choose basic mode for read-only API tests or enhanced mode for full CRUD testing.

Instructions

Run comprehensive tests on all Todoist MCP features to verify functionality

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_test_all_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoTest mode: 'basic' for read-only API tests, 'enhanced' for full CRUD testing (default: basic)basic

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention potential side effects (e.g., data modification in enhanced mode), cleanup behavior, or what constitutes successful testing. This leaves the agent unaware of possible state changes.

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

Conciseness5/5

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

The description is a single sentence that is front-loaded with the action. It contains no extraneous words and efficiently conveys the core purpose.

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

Completeness2/5

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

Given the tool's nature (comprehensive testing) and the presence of many sibling tools, the description is incomplete. It does not explain what output to expect, duration, or any prerequisite state. For a test tool, this information is critical for proper use.

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

Parameters3/5

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

The input schema has 100% description coverage for the 'mode' parameter, including an explanation of 'basic' vs 'enhanced'. The tool description does not add additional parameter meaning, but the schema already suffices. Baseline 3 is appropriate.

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

Purpose4/5

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

The description clearly states it runs comprehensive tests on all Todoist MCP features, with a specific verb (run) and resource (Todoist MCP features). It distinguishes from sibling test tools like todoist_test_connection and todoist_test_performance by testing all features comprehensively. However, the missing title is a minor missed opportunity.

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 (e.g., specific test tools). There is no mention of prerequisites, when not to use, or typical scenarios. The description lacks context for decision-making.

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