Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Detect duplicate tickets

customer-support_ticket-deduplicate

Find duplicate tickets for the same email address and repeated wording across customers. Each pair names the rule and a confidence level. Tickets are not merged. Price $0.05 USDC. POST /api/v1/customer-support/ticket-deduplicate. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "customer-support_ticket-deduplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
ticketsNo
messagesNo
policiesNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full load and does well: it discloses the non-destructive behavior ('Tickets are not merged'), the return shape ('Each pair names the rule and a confidence level'), the cost ($0.05 USDC), the endpoint, and the payment failure mode (402, no execution). It omits batching limits, idempotency, and what an empty result means, which keeps it from a 5.

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?

Five short sentences, front-loaded with the purpose, then output shape, side-effect disclaimer, pricing, and endpoint. Nothing is redundant, though the endpoint and price sentences are operational detail placed before any input guidance.

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 tool with 8 parameters, deeply nested input objects, no output schema, and no annotations, the description covers outcome and billing but leaves the entire input contract unexplained. An agent would know what the tool does and what it costs, but not how to shape a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, several nested (tickets, messages, policies, categories, file), yet the description never mentions a single parameter or explains the four alternative input modes (tickets/csv/json/text/file). The only indirect hint is that input contains email addresses and ticket text. An agent must reverse-engineer the schema to choose an input form.

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?

States a specific verb and resource ('Find duplicate tickets') and even names the two detection rules used: same email address and repeated wording across customers. This makes it clearly distinct from classify/prioritize/summarize siblings. It does not explicitly differentiate itself from the similarly-named escalation-detect, so it stops short of a 5.

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 statement of when to call this versus the sibling detection/audit tools, and no preconditions discussed. The only usage-adjacent information is the negative constraint 'Tickets are not merged', which tells the agent about side effects rather than when this tool is the right choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources