lendlord-mcp

Update task

update_task

Edit a Lendlord task's subject, description, due date, or status to completed, active (reopen), or deleted using its task ID.

Instructions

Edit a task, or change its status: completed, active (reopen) or deleted.

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": {
      "taskId": "<taskId>"
    },
    "name": "update_task"
  }
}

Input Schema

Name	Required	Description
`status`	No
`taskId`	Yes
`confirm`	No	Set true once the user has approved writes for this session
`dueDate`	No
`subject`	No
`description`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 15, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the write nature is known. The description adds the genuinely useful semantic that status='active' means reopen and that 'deleted' is reachable through this single tool, which the enum list alone does not explain. However, there is tension with destructiveHint=false that is never resolved (soft-delete vs. real deletion), and no note about reversibility or the confirm prerequisite.

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?

A single well-formed sentence with the action and the status values front-loaded and no filler. Its brevity is appropriate in form, though it borders on under-specification for a six-parameter mutation tool.

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?

For a write tool with six parameters, 17% schema coverage and no output schema, the description is too thin. It never says which fields are editable, that deletion is permanent or recoverable, or that `confirm` is required when writing.

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?

Schema description coverage is only 17% (just `confirm`), so the description must compensate. It does clarify the meaning of the one enum valueset (completed / active=reopen / deleted), which is real added meaning, but leaves taskId, dueDate, subject, description and the confirm flag entirely unexplained.

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?

States a specific verb (edit/change) on a specific resource (task), and enumerates the status transitions including the 'active (reopen)' semantics. It is distinguishable from create_task and list_tasks, though it does not name those siblings to differentiate scope explicitly.

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 on when to use this tool versus alternatives, and no exclusions. Critically, it does not mention the `confirm` gate that the schema says must be set before writes are approved, so an agent gets no workflow guidance beyond the bare action.

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