Skip to main content
Glama

Caelara Labs E-Commerce Intelligence

review_sentiment_parser

Score review sentiment with aspect breakdown (quality, price, shipping, fit, service)

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": "review_sentiment_parser"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoNewline-separated reviews
reviewsNoArray of review strings or {text, rating}

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 burden and discloses almost no behavioral traits. It doesn't say whether one of text/reviews is required (both are marked optional), how the two inputs differ, what the scoring scale is, or whether aspects not present in a review are omitted or zero-filled. For a scoring tool with no output schema, this is a meaningful gap.

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?

A single front-loaded sentence with zero filler; the aspect list is the only elaboration and it is directly useful. Nothing can be trimmed without losing content.

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 that returns sentiment scores across five aspects, the description never indicates the return shape or scale, and there is no output schema to fall back on. Combined with the absence of annotations and the ambiguity of two optional input paths, an agent lacks what it needs to interpret results correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters are already documented in the schema and the baseline is 3. The description adds no information about the parameters themselves — it does not clarify the newline-separated vs array distinction or whether the optional rating field on array entries influences scoring.

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 ('Score review sentiment') and adds the differentiating detail of an aspect breakdown enumerating quality, price, shipping, fit, and service. An agent can tell this apart from sibling parsers and calculators without opening the schema. It stops short of explicit sibling routing, so a 4 rather than a 5.

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 statement of when to use this tool, when not to, or which sibling to prefer instead. The agent must infer from the aspect list that this is for product-review analysis rather than generic text parsing. No prerequisites or input requirements are mentioned.

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