Skip to main content
Glama

Clôturer un ticket (conforme)

gestsup_close_ticket

Close a ticket by providing resolution (required for all) and cause (required for incidents). Validates mandatory fields, updates description, and notifies requester.

Instructions

Clôture un ticket selon son type : un INCIDENT exige la CAUSE ET la RÉSOLUTION ; une DEMANDE exige au moins la RÉSOLUTION. La clôture est REFUSÉE si une obligation manque. La cause (si fournie) est ajoutée à la fin de la description du ticket ; la résolution est consignée. Résout le ticket et notifie le demandeur. Nécessite le plugin « gestsup_mcp ».

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeNoTemps passé (minutes).
causeNoCause (ajoutée en fin de description). Obligatoire pour un incident.
notifyNoNotifier le demandeur de la clôture.
ticket_idYesNuméro du ticket.
resolutionYesRésolution : ce qui a permis de résoudre. Obligatoire (incident ET demande).
procedure_idNoID d'une procédure GestSup (kind=procedure), optionnel.
procedure_textNoProcédure en texte libre, optionnel.
Behavior4/5

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

No annotations provided; description covers validation logic, side effects (cause appended, resolution recorded, notification), and plugin requirement.

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?

Four concise sentences, front-loaded with main purpose, no fluff.

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?

Given 7 parameters (2 required) and no output schema, description covers validation, side effects, and dependencies but lacks return value info.

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 coverage is 100%; description adds context for cause and resolution (obligations, appended/recorded), time unit, and default for notify.

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?

Description clearly states it closes a ticket and distinguishes between incident and request types with specific requirements.

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

Usage Guidelines4/5

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

Explains when to use and the conditional obligations, but does not explicitly name sibling tools as alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/matmatmat763/Gestsup-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server