Skip to main content
Glama
OpenLMNP

OpenLMNP

Delete Expense

delete_expense
Destructive

Deletes an operating expense by its identifier and removes associated supporting documents; this action is irreversible.

Instructions

Supprime une charge d'exploitation 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": {
      "expense_id": "<expense_id>"
    },
    "name": "delete_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
expense_idYesIdentifiant de la charge à supprimer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.1
    • addedInput schema / properties / expense_id / description
      Added value: +"Identifiant de la charge à supprimer"
  2. First observedv0.1.1

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true, so the safety class is covered. The description adds genuinely new behavioral context beyond that: associated supporting documents are deleted as a cascade, and the action cannot be undone. It does not say whether deletion fails when the expense is referenced by other records or whether any confirmation or permission is required, which prevents a 5.

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: what it does, what else is destroyed, and the irreversibility warning. The most consequential facts are front-loaded and no sentence is redundant.

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 description covers the essentials, including the non-obvious cascading document deletion. Missing are failure conditions (e.g., expenses attached to a filed tax return) and any confirmation requirement, but the core is complete.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains expense_id. The phrase 'par son identifiant' restates that without adding format, range, or sourcing guidance. Baseline 3 applies.

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 in the first clause: deleting an operating expense by its identifier. It is clearly distinguishable from siblings like delete_income, delete_furniture, or delete_document by naming the resource precisely. It does not explicitly contrast itself with those siblings, which keeps it from a 5.

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 infers this is the tool for removing an expense. There is no statement about when to prefer it over update_expense or delete_document (e.g., when the whole record should go versus being corrected or the receipt detached), and no preconditions are given.

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