Skip to main content
Glama
Sign In
GLPI MCP

GLPI MCP

by USONDIG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

delete_supplier

Remove a supplier from GLPI. By default, moves it to trash for reversible deletion; set purge=true for permanent removal that also clears linked contracts, contacts, assets, and tickets.

Instructions

Supprime un fournisseur.

  • purge=False (défaut) : mise à la corbeille, réversible via update_supplier(supplier_id, {"is_deleted": 0})

  • purge=True : suppression définitive et IRRÉVERSIBLE, qui retire aussi les rattachements du fournisseur à ses contrats, contacts, matériels et tickets. À n'utiliser que sur un doublon ou une saisie erronée.

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": {
      "supplier_id": "<supplier_id>"
    },
    "name": "delete_supplier"
  }
}

Input Schema

NameRequiredDescriptionDefault
purgeNo
supplier_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and discloses key traits: soft-delete vs permanent deletion, reversibility, and cascade effects on related entities. It does not mention required permissions or rate limits, but the core destructive behavior and side effects are clearly surfaced.

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?

The description is front-loaded with the core action, then uses a bullet list for the purge modes and a final caution. Every sentence adds necessary information with no filler.

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 2-parameter mutation tool with no output schema and no annotations, the description covers the essential behavioral details: default vs purge behavior, reversibility, cascade effects, and usage context. Nothing critical is missing that would prevent correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It thoroughly explains the purge parameter (default false, reversible vs irreversible, cascade effects), though supplier_id is only implied by context and not further described. This adds substantial meaning beyond the bare schema.

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 states a specific verb ('Supprime') and resource ('un fournisseur'), making clear it deletes a supplier. It also distinguishes this from the recovery path via update_supplier, so an agent can tell it apart from siblings like update_supplier and delete_contact.

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

Usage Guidelines5/5

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

It explicitly describes two modes: purge=False (reversible via update_supplier) and purge=True (irreversible, also removes links to contracts, contacts, materials, and tickets). It ends with a clear condition: only use it on a duplicate or an erroneous entry, which is exactly the when-to-use guidance needed.

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

Deploy Server

Other Tools