Skip to main content
Glama
Sign In

AppmanAi

by com.appmanai
OverviewDiscussionsAdmin

App rating over time

app_metrics_ratings_history
Read-only

An app's average rating and star breakdown over time in one country — a dated series for charting whether a release helped or hurt. app_metrics_ratings_worldwide gives the current picture across all countries instead. Costs 5 credits.

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": {
      "store": "<store>",
      "country": "<country>",
      "package": "<package>"
    },
    "name": "app_metrics_ratings_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
packageYesApp package / bundle id, e.g. "com.discord" (Android) or a numeric App Store id. If you only have the app name, call app_search first to resolve it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds two things beyond that: a concrete cost ("Costs 5 credits") and the shape of the result (a dated rating/star-breakdown series), both of which an agent needs for budgeting and planning. It omits retention depth and granularity, keeping it short of a 5.

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 sentences plus a cost clause. The purpose and scope lead, the sibling contrast follows, and the operational cost is appended last — every clause carries information.

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 describing the return as a dated series of average rating and star breakdown. Combined with the cost disclosure, an agent has enough to call it correctly; only the time span and update cadence are left implicit.

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 100%, so store, country, and package are fully documented in the schema, including the app_search fallback for resolving package. The description reinforces the single-country scoping but adds no syntax or format detail beyond the schema; baseline 3 applies.

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?

"An app's average rating and star breakdown over time in one country — a dated series" states a specific resource, metric set, and scope. It explicitly names app_metrics_ratings_worldwide as the contrasting tool, so an agent can separate the two without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a concrete use case ("charting whether a release helped or hurt") and routes the worldwide/current-snapshot need to the sibling tool. It doesn't state prerequisites or when the historical series is not appropriate, so it stops short of full routing guidance.

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

All AppmanAi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources