Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Classify support tickets

customer-support_ticket-classify

Classify supplied tickets into billing, access, outage, defect, delivery, or account when one documented keyword list has the most matches. A caller-supplied category list replaces that set. A tie stays unclassified. Price $0.03 USDC. POST /api/v1/customer-support/ticket-classify. 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-classify"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
ticketsNo
messagesNo
policiesNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: pricing at $0.03 USDC, 402 on unpaid calls with no execution, and deterministic tie handling. However, it says nothing about what a caller receives back (per-ticket label? confidence? unmatched flag?) and nothing about which of the several input channels are equivalent — meaningful gaps for a paid mutation-free but billed endpoint.

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?

Front-loaded with the decision rule, then override behavior, then tie handling, then commercial/transport facts — no filler sentences. The pricing, endpoint, and 402 lines are telegraphic but each conveys a distinct operational fact.

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 an 8-parameter tool with nested objects, multiple alternate input formats, no annotations, and no output schema, the definition is thin: the response shape is never described and the mutually exclusive text/csv/json/file inputs are unexplained. Only the classification rule and billing behavior are complete.

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, so the description must compensate, and it only touches 'tickets' and 'categories' — the latter usefully explained as replacing the default set. The csv/file/json/text alternative input channels, plus messages and policies, are never mentioned, leaving an agent to guess precedence among content sources and the role of nested message and policy objects.

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?

Names a specific verb (classify), resource (supplied tickets) and enumerates the fixed output labels (billing, access, outage, defect, delivery, account), which makes it clearly distinct from siblings like ticket-prioritize or ticket-deduplicate. The phrase 'one documented keyword list' is slightly opaque — it is not stated where that list lives, though the categories parameter later implies it.

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

Usage Guidelines4/5

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

Gives the operative condition for classification (the category with the most keyword matches wins), explains the override path (a caller-supplied category list replaces the default set), and states the tie outcome (unclassified). It does not contrast explicitly with sibling tools such as prioritize or escalation-detect, so the agent must infer routing from the purpose statement.

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