Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Draft a support reply

customer-support_resolution-suggest

Draft a reply that quotes the customer and a supplied policy only when that policy shares a word with the ticket. The draft does not resolve the ticket or state an unsupplied policy. Price $0.05 USDC. POST /api/v1/customer-support/resolution-suggest. 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_resolution-suggest"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
ticketsNo
messagesNo
policiesNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses the $0.05 USDC cost, the POST endpoint, and critically that unpaid calls return 402 and do not run — a failure mode an agent must know. It also states output constraints (no invented policy, no resolution). What it never says is what the returned draft looks like or how long it is, but the payment/failure disclosure is well above the norm.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short sentences, all front-loaded: the grounding rule comes first, then the negative scope, then cost and transport, then the failure mode. Nothing is padded and every sentence carries information an agent needs.

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, zero schema documentation, no annotations, and no output schema, the description leaves major gaps: the relationship among the four input modalities is unexplained, and with no output schema the shape and content of the returned draft are never described. The payment mechanics are covered well, but the data contract is 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?

Schema description coverage is 0% across 8 parameters, several of them nested (tickets with messages, policies, categories) plus four alternate payload modes (csv, file, json, text). The description only implicitly gestures at tickets/policies/customer and never explains the mutual exclusivity or precedence of the csv/file/json/text inputs, so the caller is left guessing on most of the surface.

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+resource ('Draft a reply') and immediately scopes it with the grounding rule that a policy may be quoted only when it shares a word with the ticket. That is far more informative than the name alone and clearly separates it from summarize/detect/audit siblings, though it never names those siblings to contrast 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 description gives behavioral constraints (quote only on word overlap, no unsupplied policy, does not resolve the ticket) which implicitly tells the caller this is a drafting step, not a resolution step. However there is no explicit when-to-use/when-not guidance or reference to an alternative tool for the cases this one refuses to handle.

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