Skip to main content
Glama

sentiment_trend

Read-only

Tracks daily or weekly positive, neutral, and negative review counts with average ratings for an app, helping you spot sentiment shifts over time.

Instructions

Positive / neutral / negative counts and average rating per day or week.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "app": "<app>"
    },
    "name": "sentiment_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
appYesGame slug, e.g. critical-strike.
daysNo
bucketNoday

Output Schema

NameRequiredDescriptionDefault
appYes
bucketYes
pointsYes
period_endYes
period_startYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the useful behavioral fact that output is aggregated counts plus an average rating rather than raw records. It does not disclose the lookback default, the 365-day ceiling, or that a narrow window with week bucketing yields very few data points.

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?

A single telegraphic noun phrase with zero filler and the key output dimensions front-loaded. It is efficient, though the missing verb makes it read more like a label than a definition.

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

Completeness3/5

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

An output schema exists, so return values need no prose explanation, and one of three parameters is covered. What remains missing is the days-window behavior and any routing signal versus the four sibling tools, which for a trending/aggregation tool leaves a noticeable gap.

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 coverage is only 33% — just the app slug is documented — so the description carries the burden and only partially meets it. "per day or week" maps to the bucket enum, but the days parameter is never mentioned: its default of 30, its 365 max, and how window size interacts with bucket granularity are all left unstated.

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?

The description names a specific resource and output shape: positive/neutral/negative counts plus average rating, bucketed per day or week. That is concrete enough to distinguish it from a raw review listing, though it never says explicitly that results are scoped to one app, nor does it contrast itself with siblings like search_reviews or top_issues.

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 guidance at all — nothing says to reach for this tool when the user asks for sentiment over time rather than individual reviews or issue rankings. The day/week concept hints at trend analysis, but the agent must infer that alternative and any preconditions on its own.

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