Skip to main content
Glama

Review stats

get_stats
Read-only

Average rating, review count, rating distribution and reply rate, for everything or one location or platform. Default period: the last 12 months.

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

Input Schema

NameRequiredDescriptionDefault
sinceNoStart of the period, on or after. Default: 12 months before until.
untilNoEnd of the period, before this date or time. Default: now.
platformNo
location_idNoOnly this location (from list_locations).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / location_id / description
      Added value: +"Only this location (from list_locations)."
    • changedInput schema / properties / since / description
      Previous value: -"A date (2026-10-01) or an ISO 8601 timestamp."New value: +"Start of the period, on or after. Default: 12 months before until."
    • changedInput schema / properties / until / description
      Previous value: -"A date (2026-10-01) or an ISO 8601 timestamp."New value: +"End of the period, before this date or time. Default: now."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds useful context in the default 12-month window, but says nothing about whether location_id and platform can be combined, or what happens when no data matches.

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?

Two short sentences, metrics front-loaded, with the default period placed as a trailing caveat. Nothing is wasted and the most decision-relevant information comes first.

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?

With no output schema, the description compensates by enumerating the four values returned, which is exactly what an agent needs to decide whether this tool answers the question. Minor gaps remain around combining filters and empty-result behavior, but the core is complete for a zero-required-parameter read tool.

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 75%, so since/until/location_id are already documented in the schema and the description merely restates the 12-month default. It does clarify that platform and location act as scope selectors on the aggregate, which is a small but real addition over the enum list.

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 the exact metrics returned (average rating, review count, rating distribution, reply rate) and the aggregation scope (everything, one location, or one platform). That distinguishes it clearly from get_review and list_reviews, though it never names a sibling 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 phrase 'for everything or one location or platform' implies when this aggregate view is appropriate versus per-review tools, and the default period is stated. However, there is no explicit when-to-use/when-not guidance and no mention of how to narrow further if the result set is large.

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