Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Prioritize support tickets

customer-support_ticket-prioritize

Set priority from a supplied severity and from documented urgency and business-impact phrases. A ticket with none of those signals stays unspecified. Price $0.04 USDC. POST /api/v1/customer-support/ticket-prioritize. 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-prioritize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
ticketsNo
messagesNo
policiesNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load, and it does disclose the paid-call mechanics: $0.04 USDC, POST endpoint, and 402 on unpaid calls preventing execution. It omits other important traits such as batch behavior (the schema allows up to 200 tickets), whether tickets are mutated or a result set is returned, and idempotency, leaving meaningful gaps for a mutation-shaped tool.

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 with the core behavior front-loaded, followed by the fallback rule and payment/endpoint logistics. No filler; every sentence carries information, though the endpoint string is arguably less valuable to an agent than parameter guidance would be.

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 complex tool with 8 undocumented parameters, nested objects, and no output schema or annotations, the description covers pricing and the no-signal case but leaves the input contract and return shape unexplained. An agent would not know which of the alternative input forms to supply or what it receives back.

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 largely does not. It references severity and impact-like phrases, which loosely maps to the tickets[].severity and tickets[].impact fields, but says nothing about the top-level input modes (csv, json, text, file, tickets) or the messages, policies, and categories inputs.

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 ('Set priority' on tickets) and names the signals that drive the decision (supplied severity, documented urgency/business-impact phrases). An agent can tell this apart from siblings like sentiment-analyze or escalation-detect without opening the schema, though no sibling is named 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 fallback rule ('a ticket with none of those signals stays unspecified') tells the agent what happens in the no-signal case, which implicitly bounds when the tool is useful. However, there is no explicit when-to-use versus when-to-use-a-sibling guidance or precondition for calling it over classify or escalation-detect.

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