Skip to main content
Glama
FreeScout MCP Server

FreeScout MCP Server

Get FreeScout Ticket

freescout_get_ticket
Read-only

Retrieve and analyze a FreeScout ticket by ID or URL to inspect its details, with optional conversation threads for support triage and response planning.

Instructions

Fetch and analyze a FreeScout ticket by ID or URL

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

Input Schema

NameRequiredDescriptionDefault
ticketYesTicket ID, ticket number, or FreeScout URL
includeThreadsNoInclude conversation threads in the result; false omits them from the output

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.2.0
    • changedInput schema / properties / includeThreads / description
      Previous value: -"Include all conversation threads"New value: +"Include conversation threads in the result; false omits them from the output"
  2. Changed1 schema field 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"
  3. First observedv2.1.1

TDQS

C2.7/5.0
Behavior2/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 nothing beyond that: it does not explain what 'analyze' entails, whether the call is read-only against a remote instance, or how the includeThreads default affects output volume.

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 with no filler and the action front-loaded. It is efficiently written, though the brevity borders on under-specification rather than genuine conciseness.

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?

The tool is simple, annotations cover safety, and the schema fully documents both parameters, so little is strictly missing. The undefined 'analyze' claim and the lack of differentiation from similar siblings leave a real gap for correct tool selection.

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 both parameters are already documented in the schema, and the description only echoes the accepted forms of the ticket identifier. Baseline 3 is appropriate; the description does not clarify what omitting threads changes in practice.

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?

The description names a specific verb ('Fetch') and resource ('FreeScout ticket') with the selector ('by ID or URL'), so the basic action is recoverable. However, the trailing 'and analyze' is undefined and blurs the line with siblings such as freescout_analyze_ticket and freescout_get_ticket_context, so an agent cannot reliably tell this apart from those tools.

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 exclusions, and no reference to alternatives. The description never says when an agent should call this rather than freescout_get_ticket_context or freescout_analyze_ticket, leaving routing to inference from names alone.

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