Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_ecom_review_sentiment_parser

Scores e-commerce review sentiment with aspect breakdowns for quality, price, shipping, fit, and service, turning raw review text into structured insight.

Instructions

[E-Commerce Intelligence] Score review sentiment with aspect breakdown (quality, price, shipping, fit, service) Measured p50 11 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://ecom.caelaralabs.com.

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": "caelara_ecom_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 observedv1.0.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add useful operational context: a remote endpoint and measured latency (p50 11 ms / p95 15 ms, dated). However, it never states that the operation is non-mutating, what the response contains or how scores are scaled, or whether mixing 'text' and 'reviews' is an error.

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?

Two tight sentences, front-loaded with the purpose before the benchmark and host metadata. The latency parenthetical with a date and domain is mildly extraneous for tool selection, but nothing is padded or redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter optional-input scoring tool with no output schema, the description gives enough to call it correctly: what it produces (per-aspect sentiment) and where it runs. The remaining gap is that the return shape and scoring scale are unspecified even though no output schema exists to cover them.

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% for both parameters, so the baseline is 3. The description's aspect list (quality, price, shipping, fit, service) describes output dimensions rather than clarifying the parameters, and the precedence between 'text' and 'reviews' is left entirely to the schema.

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

Purpose5/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') plus the differentiating output ('aspect breakdown (quality, price, shipping, fit, service)'). No sibling tool in the catalog does sentiment scoring, so an agent can route to it unambiguously from the name and first clause alone.

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 '[E-Commerce Intelligence]' tag and 'review' framing imply the domain of use, but there is no explicit when-to-use, when-not-to-use, or named alternative. Nothing tells the agent how to choose between the 'text' and 'reviews' inputs or what to do with reviews that already carry a rating.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools