db4app Todo MCP Server

mark_as_done

Complete tasks by marking todo items as done using their unique ID. This tool updates the todo list application to reflect completed items.

Instructions

Mark a todo item as completed. Use this when the user wants to complete a task. Provide the todo ID.

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": {
      "todo_id": "<todo_id>"
    },
    "name": "mark_as_done"
  }
}

Input Schema

Name	Required	Description
`todo_id`	Yes	The ID of the todo item to mark as completed
`postgresUrl`	No	Override the Postgres connection URL (defaults to MCP_POSTGRES_URL)
`connectionId`	No	Browser connection ID (used to construct connection URL if postgresUrl not provided)
`authToken`	No	Auth token for authentication (used to construct connection URL if postgresUrl not provided)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jan 11, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('mark as completed') but doesn't explain what this entails—whether it updates a status field, adds a timestamp, triggers notifications, or has side effects like archiving. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 extremely concise—two sentences that directly state the purpose and usage without any fluff. It's front-loaded with the core action, and every sentence serves a clear purpose, making it efficient and easy to parse.

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 complexity (a mutation with 4 parameters) and the absence of both annotations and an output schema, the description is insufficient. It doesn't cover behavioral aspects like what 'completed' means, error handling, or return values, leaving the agent with incomplete information for safe and effective 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 schema description coverage is 100%, meaning all parameters are well-documented in the input schema itself. The description adds minimal value by mentioning 'todo ID' but doesn't provide additional context beyond what the schema already covers (e.g., format details or usage tips). This meets the baseline for high schema coverage.

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 the verb ('mark as completed') and resource ('todo item'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'add_todo' and 'list_todos' by focusing on completion rather than creation or listing. However, it doesn't explicitly differentiate from 'remove_todo' in terms of action outcome.

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

Usage Guidelines3/5

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

The description provides basic usage context ('when the user wants to complete a task'), which implies when to use this tool. However, it doesn't offer explicit guidance on when NOT to use it or mention alternatives like 'remove_todo' for deletion instead of completion. The guidance is present but lacks depth for optimal 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