Skip to main content
Glama
FreeScout MCP Server

FreeScout MCP Server

Analyze FreeScout Ticket

freescout_analyze_ticket
Read-only

Analyze a FreeScout ticket to identify the issue type, root cause, and suggested solution, enabling support teams to diagnose and resolve customer issues.

Instructions

Analyze a FreeScout ticket to determine issue type, root cause, and suggested solution

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_analyze_ticket"
  }
}

Input Schema

NameRequiredDescriptionDefault
ticketYesTicket ID, ticket number, or FreeScout URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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"
    • changedOutput schema / (root)
      Previous value: -{
      -  "$schema": "http://json-schema.org/draft-07/schema#",
      -  "additionalProperties": false,
      -  "properties": {
      -    "attachments": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "codeSnippets": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "customerEmail": {
      -      "format": "email",
      -      "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      -      "type": "string"
      -    },
      -    "customerName": {
      -      "type": "string"
      -    },
      -    "errorMessages": {
      -      "items": {
      -        "type": "string"
      -      },
      -      "type": "array"
      -    },
      -    "hasAttachments": {
      -      "type": "boolean"
      -    },
      -    "isBug": {
      -      "type": "boolean"
      -    },
      -    "isReproducible": {
      -      "type": "boolean"
      -    },
      -    "isThirdPartyIssue": {
      -      "type": "boolean"
      -    },
      -    "issueDescription": {
      -      "type": "string"
      -    },
      -    "rootCause": {
      -      "type": "string"
      -    },
      -    "suggestedSolution": {
      -      "type": "string"
      -    },
      -    "testedByTeam": {
      -      "type": "boolean"
      -    },
      -    "ticketId": {
      -      "type": "string"
      -    }
      -  },
      -  "required": [
      -    "ticketId",
      -    "customerName",
      -    "customerEmail",
      -    "issueDescription",
      -    "hasAttachments",
      -    "attachments",
      -    "codeSnippets",
      -    "errorMessages",
      -    "isReproducible",
      -    "testedByTeam",
      -    "isBug",
      -    "isThirdPartyIssue"
      -  ],
      -  "type": "object"
      -}New value: +null
  2. First observedv2.1.1

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the analysis yields a classification, a root cause, and a suggested solution, which is useful context beyond the annotations, but it does not disclose how the analysis is produced, whether it requires extra API calls, or its reliability.

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

Conciseness4/5

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

A single short sentence, front-loaded with the verb and resource and followed by the concrete outputs. Nothing is wasted, though the brevity leaves room for a usage sentence that would earn its place.

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

Completeness3/5

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

For a one-parameter read-only tool with a fully described schema and no output schema, the description covers the essentials of what the tool returns at a high level. It omits the structure of the analysis result and when to prefer it over sibling retrieval tools, which matters for a diagnostic tool that sits beside freescout_get_ticket.

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% and the single parameter is fully documented as accepting a ticket ID, ticket number, or FreeScout URL. With one well-documented parameter, the schema carries the semantics and the description does not need to repeat them.

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?

The description states a specific verb and resource ('Analyze a FreeScout ticket') and names the three outputs it produces: issue type, root cause, and suggested solution. That distinguishes it from siblings like freescout_get_ticket or freescout_update_ticket, which fetch or mutate rather than diagnose.

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?

The description gives no when-to-use guidance, no prerequisites, and does not route the agent to or away from siblings such as freescout_get_ticket_context, which sounds adjacent. The agent must infer that this tool is for diagnosis rather than retrieval.

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