Skip to main content
Glama
FreeScout MCP Server

FreeScout MCP Server

Update Ticket Status/Assignment

freescout_update_ticket
Destructive

Update a FreeScout ticket's status or assignment by specifying the ticket ID, new status, and assignee to keep helpdesk workflows current.

Instructions

Update ticket status and/or assignment

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": {
      "ticket": "<ticket>"
    },
    "name": "freescout_update_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoNew ticket status
ticketYesTicket ID, ticket number, or FreeScout URL
userIdNoUser ID recording this update (default: from env)
assignToNoUser ID to assign the ticket to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / userId
      Added value: +{
      +  "description": "User ID recording this update (default: from env)",
      +  "type": "number"
      +}
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "message": {
      -      "type": "string"
      -    },
      -    "success": {
      -      "type": "boolean"
      -    },
      -    "ticketId": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "success",
      -    "message",
      -    "ticketId"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. First observedv2.1.1

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered externally. The description adds nothing beyond them: it does not say that closing or marking spam changes what the customer sees, whether assignment triggers notification, or that userId defaults from the environment. No contradiction exists, but the description contributes no behavioral context of its own.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single five-word phrase is front-loaded and free of waste, but for a destructive four-parameter mutation tool it is under-specified rather than concise. There is no structure to speak of, and the brevity leaves real gaps unaddressed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive write tool with no output schema, the description should explain what changes are applied, what side effects follow (customer notification, assignment handoff), and how partial updates behave when only one field is supplied. None of that is present, so the definition is incomplete relative to the tool's risk and complexity.

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 description coverage is 100%, so every parameter including the status enum and the ticket identifier formats is already documented in the schema. The description mentions status and assignment but adds no format, default, or interaction detail beyond what the schema states, making the baseline 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update ticket status and/or assignment" names a verb and resource and identifies the two mutable fields, so the basic action is understandable. However, it essentially restates the title verbatim and gives no differentiation from siblings like freescout_get_ticket or freescout_add_note, leaving the agent to infer scope.

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 guidance, no mention of prerequisites (does the ticket need to be open? does the user need permission?), and no reference to alternatives such as adding a note or creating a reply. The agent must guess that this is the tool for changing state rather than communicating with the customer.

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