Skip to main content
Glama

BRAINIAC Customer Support Intelligence

Analyze ticket sentiment

customer-support_sentiment-analyze

Label customer wording with a documented positive and negative word list. Text with no listed words stays unspecified. Price $0.03 USDC. POST /api/v1/customer-support/sentiment-analyze. 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_sentiment-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
textNo
ticketsNo
messagesNo
policiesNo
categoriesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose two valuable traits: a $0.03 USDC cost and a 402 failure mode where 'unpaid calls... do not run'. However, it says nothing about the eight input modes it accepts (csv, file, json, text, tickets, messages, policies, categories), whether they are alternatives or combined, what the response looks like, or any size/rate limits beyond the schema's maxLengths.

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?

Five short, front-loaded sentences with no filler; the lexicon method and fallback rule come first, then cost and transport details. The literal endpoint path is mildly redundant but still operational information.

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 8 mostly nested parameters, no annotations, and no output schema, the description is far too thin — it never explains the input surface, how multiple text sources combine, or what the labels come back as. Only the pricing and 402 behavior fill genuine gaps.

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?

Schema description coverage is 0% across 8 parameters, including deeply nested objects, and the description mentions none of them. An agent cannot learn from either source what 'policies' or 'categories' (with their name/keywords pairs) do in a word-list sentiment tool, or whether 'file'/'csv'/'json' are mutually exclusive alternatives.

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 ('Label customer wording') and discloses the exact mechanism (a documented positive/negative word list), which is genuinely useful. It does not distinguish this from siblings such as ticket-classify or escalation-detect, so an agent must guess at boundaries, but the core operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative among the many ticket-processing siblings. The only routing-adjacent information is the fallback rule ('Text with no listed words stays unspecified'), which describes an outcome rather than when to choose this tool.

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