Skip to main content
Glama
OpenLMNP

OpenLMNP

Delete Income

delete_income
Destructive

Delete a rental income record by its ID to correct or remove entries. This action is irreversible, so verify the identifier before proceeding.

Instructions

Supprime un revenu locatif par son identifiant. 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": {
      "income_id": "<income_id>"
    },
    "name": "delete_income"
  }
}

Input Schema

NameRequiredDescriptionDefault
income_idYesIdentifiant du revenu à supprimer

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, so the safety profile is covered structurally. The description adds that the action is irreversible ('Cette action est irréversible'), which sharpens the consequence slightly, but says nothing about permissions, cascade effects on related computations, or whether confirmation is expected.

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 short sentences with zero filler; the action and the irreversibility warning are both front-loaded.

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 single-parameter delete tool with full schema coverage and no output schema, the definition covers what the agent needs to invoke it correctly. Only cross-tool routing guidance is missing.

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 documented parameter (income_id, 'Identifiant du revenu à supprimer'). The description's 'par son identifiant' mirrors the schema without adding format, range, or validity details, so the 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?

States a specific verb and resource ('Supprime un revenu locatif') plus the lookup key ('par son identifiant'), so the agent knows exactly what the tool does. It does not explicitly contrast with siblings like update_income or delete_expense, but the resource is named unambiguously enough to differentiate.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no mention of prerequisites, and no reference to alternatives such as update_income for non-destructive changes. Usage is only implied by the verb 'Supprime'.

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