cpp-espace-mcp

Overview Schema Source Related Servers Discussions Admin

update-work-order-task

Update work order task details such as description, due date, estimated minutes, or completion status. Always confirm with user.

Instructions

Update a task on a work order. ALWAYS confirm with user before calling.

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-work-order-task"
  }
}

Input Schema

Name	Required	Description
`taskId`	Yes	Task ID to update
`Description`	No	Updated description
`DueDate`	No	Updated due date (ISO format)
`TotalMinutes`	No	Updated estimated minutes
`IsCompleted`	No	Mark task as completed

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description should disclose behavioral details. It only mentions user confirmation, lacking information on whether updates are irreversible, permissions needed, or return values.

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?

The description is extremely concise with two sentences, no wasted words. However, it could be slightly more structured without increasing length.

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 5 parameters, no output schema, and no annotations, the description is too minimal. It lacks context on what the update returns, error scenarios, prerequisites, or behavior for unmentioned fields.

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 coverage is 100% with each parameter described. The description adds no additional meaning beyond what the schema already provides, meeting the baseline expectation.

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 'Update a task on a work order' clearly states the action and resource. It is distinct from sibling tools like add-work-order-task (create) and get-work-order-tasks (list), but does not explicitly differentiate from update-work-order, though the resource differs.

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 instruction 'ALWAYS confirm with user before calling' provides a guideline for safe usage, but does not specify when to use this tool versus alternatives, nor when not to use it.

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