Txa_MCP

by TXAVLOG

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

todo_manager

Add, list, remove, and clear tasks in your project's to-do list to stay organized and focused.

Instructions

Quản lý danh sách việc cần làm (TODO) cho dự án.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "todo_manager"
  }
}

Input Schema

Name	Required	Description
`task`	No	Task description (for 'add')
`index`	No	Task index (for 'remove')
`action`	Yes	Action to perform

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.0.3Aug 11, 2026

TDQS

C2.5/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only says 'manage.' It fails to mention that actions like 'remove' and 'clear' are destructive or any side effects, persistence, or error conditions. This is a significant transparency gap.

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

Conciseness3/5

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

The description is a single concise sentence, which is efficient. However, it is under-specified for a tool with multiple operations and destructive actions, and the lack of structure means it does not fully serve its 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 has multiple actions including destructive ones, and there are no annotations or output schema, the description is insufficient. It does not explain side effects, return values, or how parameters interact, leaving important gaps for an agent.

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 schema provides 100% coverage for all parameters (action enum, task, index) with clear descriptions. The tool description adds no additional parameter meaning, but since the schema is complete, the baseline of 3 is appropriate.

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

Purpose3/5

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

The description states the tool manages a TODO list for a project, which is a clear verb+resource combination. However, it does not specify the supported actions (list, add, remove, clear) or distinguish it from similar tools like cloud_todo_manager, making the purpose somewhat vague.

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?

There is no guidance on when to use this tool versus alternatives such as cloud_todo_manager. The description does not mention any prerequisites, exclusions, or preferred scenarios, leaving the agent without explicit usage direction.

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