Skip to main content
Glama

vwork_update_task

Update a task or doc in a progress table by code or collection/doc_id, sending only fields that changed. Write access must be enabled.

Instructions

Cập nhật một task/doc trong bảng tiến độ (theo code A01/E02 hoặc collection/doc_id). Chỉ gửi field cần đổi. Yêu cầu VWORK_ALLOW_WRITE=true.

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": {
      "reference": "<reference>"
    },
    "name": "vwork_update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoghi chú
statusNotrạng thái mới, vd Đang làm
projectNoProject id, mặc định lấy từ VWORK_PROJECT (trang tiến độ dùng "eoffice")
referenceYescode (vd A01) hoặc collection/doc_id (vd tasks/E02)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose two important behaviors the schema doesn't: that this is a partial update (send only changed fields) and that a write gate (VWORK_ALLOW_WRITE=true) must be satisfied. It stops short of describing failure behavior, whether the operation is reversible, or whether it creates a missing doc.

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?

Three short sentences, front-loaded with the action and target, then the partial-update rule, then the write prerequisite. Nothing is padded, though the permission requirement could be folded into the guidance rather than tacked on as a final clause.

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

Completeness3/5

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

For a mutation tool with no annotations and no output schema, the description covers the essentials: target addressing, partial update, and the write gate. It is still incomplete on error semantics and on whether a reference that doesn't resolve creates a new doc or fails, which matters for an agent deciding to call it.

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 100%, so the schema already documents all four parameters including the reference format. The description adds the partial-update rule, which is genuinely useful, but repeats rather than extends the reference-format semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (Cập nhật / update) and resource (task/doc trong bảng tiến độ), and clarifies the two ways to address the target (code A01/E02 or collection/doc_id). It is distinguishable from siblings like vwork_tracker_docs and vwork_tracker_search, though it never names those siblings explicitly.

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?

'Chỉ gửi field cần đổi' tells the agent this is a partial update and 'Yêu cầu VWORK_ALLOW_WRITE=true' gives a prerequisite. However there is no guidance on when to use this versus the tracker siblings, and no statement of when not to use it or what an invalid reference means.

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