Skip to main content
Glama
FreeScout MCP Server

FreeScout MCP Server

Get Ticket Context

freescout_get_ticket_context
Read-only

Fetches ticket context and customer information to support drafting personalized replies.

Instructions

Get ticket context and customer info to help draft personalized replies

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

Input Schema

NameRequiredDescriptionDefault
ticketYesTicket ID, ticket number, or FreeScout URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv2.1.1

TDQS

C2.9/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 say what data is gathered, whether customer lookups can fail when no customer is linked, or how expensive the aggregation is.

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 front-loaded sentence with no filler or redundancy. It is appropriately sized, though its brevity comes at the cost of the specificity noted in other dimensions.

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?

With one parameter and no output schema, the description should clarify what "context" comprises, since return content is the tool's whole value and nothing else documents it. The safety annotations cover the rest, keeping this from being a severe gap.

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?

Only one parameter, and the schema already documents it fully ("Ticket ID, ticket number, or FreeScout URL") at 100% coverage. The description adds no further meaning such as accepted formats or fallback behavior, so the baseline 3 applies.

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?

"Get ticket context and customer info" names a verb and resource, but "context" is undefined — thread history, custom fields, customer record, or all of the above? It also fails to distinguish itself from siblings like freescout_get_ticket and freescout_analyze_ticket, which an agent could easily pick instead.

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

Usage Guidelines3/5

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

The phrase "to help draft personalized replies" implies a usage scenario but gives no explicit when-to-use versus when-not rules and names no alternative. An agent must guess whether to call this before freescout_get_ticket or freescout_create_draft_reply.

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