cpp-espace-mcp

Overview Schema Source Related Servers Discussions Admin

delete-work-order

Delete a work order by its ID to remove completed or incorrect entries from the facility management system. Confirmation required before execution.

Instructions

Delete 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": {
      "workOrderId": "<workOrderId>"
    },
    "name": "delete-work-order"
  }
}

Input Schema

Name	Required	Description	Default
`workOrderId`	Yes	Work order ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It clearly indicates the destructive nature (delete) and adds the behavioral requirement of user confirmation. This adds value beyond the action itself.

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?

Two sentences, minimal and to the point. The action is front-loaded, and the safety instruction follows immediately. Every word is earned.

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

Completeness5/5

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

For a simple delete operation with one parameter and no output schema, the description is complete: it states the purpose and provides a critical usage guideline. No additional information is necessary.

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 a single parameter (workOrderId) described as 'Work order ID to delete'. The description does not add further semantic meaning beyond what the schema already provides.

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

Purpose5/5

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

The description clearly states 'Delete a work order' which is a specific verb and resource, making it unambiguous. It distinguishes from sibling tools like create-work-order and update-work-order.

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

Usage Guidelines4/5

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

The description includes 'ALWAYS confirm with user before calling', which provides a clear usage guideline for safety. It does not mention alternatives or when not to use, but the confirmation instruction is critical.

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