Skip to main content
Glama

top_issues

Read-only

Identify recurring complaint categories in app-store reviews over a chosen lookback window, with counts, share, severity, and prior-period comparison.

Instructions

The most common complaint categories in the last days days (by primary category; praise and other excluded), with counts, share, severity, the count in the previous period of the same length, and example reviews.

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

Input Schema

NameRequiredDescriptionDefault
appYesGame slug, e.g. critical-strike.
daysNoLook-back window.
limitNo

Output Schema

NameRequiredDescriptionDefault
appYes
issuesYes
period_endYes
period_startYes
classified_reviewsYes
latest_review_dateYes
unclassified_reviewsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: the aggregation happens on primary category, praise/other are dropped, and a prior-period comparison of equal length is computed, which tells the agent how numbers relate to each other.

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 sentence that front-loads the core result (top complaint categories) and then enumerates the fields, which is efficient. The parenthetical clause about primary category and exclusions is dense but the density is justified by the information it carries.

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?

With an output schema present, the description does not need to enumerate return fields, and its field listing is partly redundant, though the prior-period mention adds value. What it omits is how `limit` shapes the result and whether output is sorted by count or by share, which matters for a 'top N' 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 coverage is 67%: `app` and `days` are documented in the schema and `days` is echoed in the description, so they add little. The `limit` parameter has no schema description and is never mentioned in the description, so its meaning (number of categories returned, capped at 12) must be inferred from the name alone.

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?

It names the exact resource and scope: the most frequent complaint categories over the last `days` days, grouped by primary category, with praise and other categories explicitly excluded. That exclusion plus the complaint-category framing makes it distinguishable from siblings like sentiment_trend or search_reviews without opening any schema.

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?

Usage is only implied by the name and the scoping clauses; there is no explicit statement of when to choose this over sentiment_trend, search_reviews, or compare_versions, nor any preconditions (e.g., minimum review volume). An agent can infer the intent but must guess the alternatives.

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