Skip to main content
Glama
OpenLMNP

OpenLMNP

Delete Property Work

delete_property_work
Destructive

Delete a property work item by its ID, including associated supporting documents. Use this irreversible action to remove work records and their attachments from OpenLMNP.

Instructions

Supprime un poste de travaux immobiliers par son identifiant. Les documents justificatifs associés sont également supprimés. Cette action est irréversible.

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": {
      "work_id": "<work_id>"
    },
    "name": "delete_property_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
work_idYesIdentifiant des travaux à supprimer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / work_id / description
      Added value: +"Identifiant des travaux à supprimer"
  2. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations only flag destructiveHint=true, and the description adds two facts an agent genuinely needs: associated supporting documents are removed too, and the action cannot be undone. It stops short of disclosing the response shape or error behavior when the ID does not exist.

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?

Three short sentences, zero filler, with the core action front-loaded and the cascade plus irreversibility following immediately.

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

Completeness4/5

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

For a one-parameter destructive tool with full schema coverage and no output schema, this covers the essential risk surface. Minor gap: it does not say whether other dependent records (expenses, furniture) linked to the work are affected or whether a not-found ID raises an error.

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% and the single work_id parameter is already documented in the schema. The description's 'par son identifiant' merely echoes that, adding no format or constraint detail beyond it.

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?

States a specific verb and resource ('Supprime un poste de travaux immobiliers') plus the lookup key ('par son identifiant'). The second sentence clarifies the cascade scope, which separates it from plain document-deletion siblings such as delete_document.

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?

Usage is only implied: the agent can infer this is the removal counterpart to create_property_work/update_property_work. There is no explicit when-to-use, when-not-to-use, or prerequisite wording (e.g., what to do if the work has linked expenses).

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