Report how this MCP server is configured and verify that the i-net HelpDesk can be reached with the current credentials. Use this first when a call fails with an authentication or connection error.

Search tickets with the same phrase syntax as the Tickets application, for example printer or Resource:"First Level Support". Returns the matching ticket ids plus suggestions for fields and values that can narrow the query further.

Read one ticket with its fields and attributes. Pass fields to limit the response to the entries you need - the full record can be large and may contain personal data.

List the ticket actions the authenticated user may currently apply to a ticket, as a map of action id to display name. The ids are the input for apply_ticket_action.

List the editing steps (history) of a ticket. For a primary ticket in a bundle the steps of its secondary tickets are merged in. Use get_ticket_step for the text of a single step.

Read one editing step of a ticket, including its text and the applied ticket action. Pass fields to reduce the returned fields and attributes.

Create a new ticket and return its id. text is the request text of the ticket. ticket_fields and action_arguments are optional and only needed for advanced cases - unknown ticket fields are rejected, unknown action arguments are ignored by the server.

Apply a ticket action to an existing ticket - answering, closing, escalating and so on - and return the id of the new editing step. Call list_ticket_actions first: only the ids listed there are valid, and they differ per ticket, user and state. This changes the ticket, so confirm the action with the user when the intent is ambiguous.