Skip to main content
Glama
Connect IQ MCP

Connect IQ MCP

by idoo

Rating distribution

store_ratings
Read-onlyIdempotent

Get an app's star-rating distribution to analyze review scores and spot rating trends. Provide the app UUID, manifest ID, or exact title to retrieve the breakdown.

Instructions

Show an app's star-rating distribution.

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

Input Schema

NameRequiredDescriptionDefault
appYesstore UUID, manifest id, or exact app title

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds only that the result is a distribution (an aggregate rather than individual records), which is modest added context; it says nothing about how the aggregation is scoped or whether it comes from a live external store.

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 short sentence with the resource front-loaded and zero filler. It is efficient, though the terseness borders on under-specification rather than tightness.

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?

For a one-parameter, read-only aggregate tool with fully documented schema and annotations, the essentials are present. However, with no output schema the description never hints at what the distribution looks like (counts per star level, percentages), leaving the return shape unspecified.

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?

With a single parameter at 100% schema description coverage, the schema already explains that "app" accepts a store UUID, manifest id, or exact app title. The description adds no additional meaning about the identifier (e.g., whether a non-exact title fails), so the schema does the heavy lifting.

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?

"Show an app's star-rating distribution" names a specific verb and resource, and the word "distribution" distinguishes it from the review-listing siblings (store_reviews_list / store_reviews_inbox). It stops short of explicitly naming an alternative, so it is clear but not sibling-differentiating at the highest level.

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: no statement that this is for aggregate rating breakdowns rather than reading individual reviews, and no pointer to store_reviews_list as the alternative for review text. The agent must infer the distinction from the noun "distribution" alone.

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