Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Summarize a support conversation

customer-support_conversation-summarize

Restate up to three customer sentences and quote supplied agent replies. The summary does not decide that a ticket was resolved. Price $0.04 USDC. POST /api/v1/customer-support/conversation-summarize. 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_conversation-summarize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
ticketsNo
messagesNo
policiesNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does usefully disclose cost ($0.04 USDC), the endpoint, payment failure behavior (402, does not run), and an output/scope bound (up to three customer sentences, no resolution verdict). However, it says nothing about input precedence among the six mutually substitutable payload options, authentication requirements, rate limits, or what the response looks like.

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 no filler, and pricing, endpoint, and payment-failure facts are stated in single clauses. The one structural weakness is ordering: output-form detail leads and the actual purpose never gets a front-loaded statement.

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?

This is a complex tool — eight parameters, six nested object types, no output schema, no annotations, and zero schema description coverage — yet the description covers only payment mechanics and a couple of output constraints. An agent would not know how to assemble a valid request from this text alone.

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

Parameters1/5

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

Eight parameters with 0% schema description coverage and no explanation in the description. The critical ambiguity — whether to supply text, csv, json, file, tickets, or messages and which wins when several are provided — is entirely unaddressed, as are the nested ticket/message/policy/category structures.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The title supplies the actual verb+resource ('Summarize a support conversation'), while the description opens with output-shape details ('Restate up to three customer sentences and quote supplied agent replies') rather than stating the operation. An agent can infer summarization, but the description itself never plainly says 'summarize this conversation' nor differentiates from siblings like sentiment-analyze or resolution-suggest.

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 by the domain wording plus the boundary note 'The summary does not decide that a ticket was resolved,' which hints that resolution judgement belongs elsewhere but never names an alternative. No explicit when-to-use, when-not-to-use, or sibling routing is given across the seven named siblings.

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