Skip to main content
Glama
OpenLMNP

OpenLMNP

Delete Furniture

delete_furniture
Destructive

Removes a furniture item by its ID, along with any supporting documents linked to it. Use this irreversible action to clean up furnishings recorded for your LMNP rental.

Instructions

Supprime un élément de mobilier 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": {
      "furniture_id": "<furniture_id>"
    },
    "name": "delete_furniture"
  }
}

Input Schema

NameRequiredDescriptionDefault
furniture_idYesIdentifiant du mobilier à supprimer

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior4/5

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

The destructiveHint annotation already flags this as a write, but the description adds two facts the annotation cannot convey: that associated supporting documents are deleted as a cascade, and that the operation is irreversible. What is missing is any mention of authorization requirements or whether the cascade is unconditional.

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 purpose, followed by the cascade side effect and the irreversibility warning. Every sentence carries distinct information with no filler.

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 no output schema, the definition covers the essentials: what is removed, the collateral document deletion, and irreversibility. It stops short of describing the confirmation or return behavior, which an agent calling blind would still want.

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% for the single furniture_id parameter, so the schema already carries the meaning. The description only restates that deletion targets an identifier and adds no format, range, or validation detail beyond it.

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 states a specific verb and resource ('Supprime un élément de mobilier') and scopes it to lookup by identifier, so it is clearly distinct from create_furniture, list_furniture and update_furniture. It does not, however, explicitly contrast itself with delete_document or explain why the related-document deletion is not the primary action.

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: an agent can infer this is the removal counterpart to create/update_furniture. There is no explicit when-to-use guidance, no statement about prerequisites (e.g. whether the item must be unused or unreferenced), and no pointer to update_furniture as the non-destructive alternative.

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