Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Audit support reply quality

customer-support_quality-audit

Check supplied replies for a resolution claim, a missing reply, or an email, amount, order, or policy that was not in the ticket. The audit does not confirm that any action happened. Price $0.12 USDC. POST /api/v1/customer-support/quality-audit. 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_quality-audit"
  }
}

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, the description carries the full burden and does meaningful work: it discloses the cost ($0.12 USDC), the transport (POST /api/v1/customer-support/quality-audit), the failure mode (unpaid calls return 402 and do not run), and a critical limitation that findings do not confirm any action occurred. It still omits rate limits, idempotency, and how to choose among the five input modes, but the disclosed economics and payment-gating behavior are substantive.

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 criteria, then scope caveat, then cost and endpoint. The operational details (price, HTTP verb, 402 behavior) earn their place for a paid endpoint; nothing is padded, though the endpoint path is the least valuable line for an agent.

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 optional parameters, five mutually exclusive-looking input formats, nested objects, no annotations, and no output schema, the description leaves the agent without the two things it most needs: which input mode to supply and what the audit returns. It explains the checks performed and the payment behavior, but nothing about the payload contract or result shape.

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?

All 8 parameters have 0% schema description coverage and the schema includes deeply nested tickets/messages/policies/categories objects, yet the description mentions no parameter by name. It never explains that csv, json, text, file, and tickets are alternative input modes or how tickets, messages, and policies interact with the audit, so an agent must reverse-engineer 200k-character limits and nested shapes unaided.

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 names a specific verb (Check) and resource (supplied replies) and enumerates exactly what it flags: a resolution claim, a missing reply, or an email, amount, order, or policy absent from the ticket. That enumeration makes it clearly distinct in practice from siblings like escalation-detect or resolution-suggest, though no sibling is named explicitly, which keeps it at 4 rather than 5.

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?

Usage is only implied: the agent learns it operates on supplied replies/tickets and that it audits rather than confirms, but there is no statement of when to choose this over conversation-summarize or escalation-detect, and no preconditions beyond payment. The scope caveat ('does not confirm that any action happened') is useful guidance but is not when-to-use routing.

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