Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Detect escalation signals

customer-support_escalation-detect

Flag a ticket when the text contains a documented escalation phrase, the priority rules mark it critical, or the same email appears on three tickets in the request. No escalation is performed. Price $0.04 USDC. POST /api/v1/customer-support/escalation-detect. 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_escalation-detect"
  }
}

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
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does meaningful work: it discloses there are no side effects ("No escalation is performed"), states a price of $0.04 USDC, and warns that unpaid calls return 402 without running. It stops short of describing the response shape or whether the flagging is deterministic, so it is strong but not complete.

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?

Four short sentences, front-loaded with the detection behavior, then the no-side-effect clarification, then cost and endpoint. The endpoint and payment sentences are useful operational facts rather than filler; a slightly tighter grouping of the commercial details would make it a 5.

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 a tool with eight parameters, nested objects, no annotations, and no output schema, the definition is thin: it never says what a "flag" response contains or which of the many input shapes to supply. Given that no output schema exists to explain return values, the description should have covered the result shape and dominant input mode, and it does not.

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?

Eight parameters exist with 0% schema description coverage, and all are nested or polymorphic (csv, file, json, text, tickets, messages, policies, categories). The description only echoes concepts like text, email, and priority rules; it never explains which input form to use, what policies/categories keywords do, or how tickets versus messages differ, so the coverage gap is left unaddressed.

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 gives a specific verb and resource ("Flag a ticket") and enumerates three concrete trigger conditions: a documented escalation phrase, priority rules marking it critical, or the same email appearing on three tickets. That detail distinguishes it in substance from siblings like ticket-prioritize or sentiment-analyze, though it never names an alternative explicitly.

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 three detection conditions implicitly tell an agent when the tool will fire, and "No escalation is performed" sets a boundary on the outcome. However, there is no explicit when-to-use guidance versus ticket-prioritize or ticket-deduplicate, and no prerequisites or input-preparation advice.

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