Skip to main content
Glama
Sign In

sonar

by app.trysonar
OverviewDiscussionsAdmin

Top Charts

sonar_top_charts
Read-onlyIdempotent

Get a store top chart (free / paid / grossing, overall or by category) with day-over-day movement: per-app rank delta, apps new to the chart, biggest movers and apps that dropped out. Use to see what's rising in a market or category. Note: summary, movers and droppedApps always describe the full top 200 — limit truncates the returned entries only. Movement is empty on the first day a chart is requested (no previous snapshot yet). Answers within about 30 seconds: when a live refresh can't finish in time the newest stored chart is returned with stale: true and its measuredAt date. Compact by default (no icon URLs or numeric ids; fields: "full" adds them). Works without an API key (free tier, limited daily use per IP).

Input Schema

NameRequiredDescriptionDefault
chartNoChart type: "free", "paid" or "grossing". Default "free".free
limitNoNumber of chart entries to return (1-200). Default 50.
storeYesApp store. "ios" for Apple App Store, "android" for Google Play.
fieldsNo"compact" (default): each app is storeId, name, developer, rating, rank, delta, isNew (movers: rank + delta; droppedApps: previousRank) — about 60% smaller. "full": adds iconUrl and numericId to every app.compact
countryNoMarket as an ISO 3166-1 alpha-2 code (e.g. "us", "gb", "de", "mt"). Nearly every App Store storefront and Google Play market works; the few small storefronts that are not supported return an error naming them. Default "us".us
categoryNoCategory key; keys differ by store (e.g. iOS "SOCIAL_NETWORKING" / "GAMES", Android "SOCIAL" / "GAME"; "HEALTH_AND_FITNESS" exists on both). An unknown key is rejected with an error. Use "overall" (default) for the store-wide chart.overall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / fields
      Added value: +{
+  "default": "compact",
+  "description": "\"compact\" (default): each app is storeId, name, developer, rating, rank, delta, isNew (movers: rank + delta; droppedApps: previousRank) — about 60% smaller. \"full\": adds iconUrl and numericId to every app.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Category key, e.g. \"HEALTH_AND_FITNESS\" (iOS) or \"HEALTH_AND_FITNESS\" / \"GAME\" (Android). Use \"overall\" (default) for the store-wide chart."New value: +"Category key; keys differ by store (e.g. iOS \"SOCIAL_NETWORKING\" / \"GAMES\", Android \"SOCIAL\" / \"GAME\"; \"HEALTH_AND_FITNESS\" exists on both). An unknown key is rejected with an error. Use \"overall\" (default) for the store-wide chart."
  3. Changed1 schema field changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO 3166-1 alpha-2 country code (e.g. \"us\", \"gb\", \"de\"). Default \"us\"."New value: +"Market as an ISO 3166-1 alpha-2 code (e.g. \"us\", \"gb\", \"de\", \"mt\"). Nearly every App Store storefront and Google Play market works; the few small storefronts that are not supported return an error naming them. Default \"us\"."
  4. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of chart entries to return (1-100). Default 50."New value: +"Number of chart entries to return (1-200). Default 50."
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +200
  5. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses several non-obvious behaviors: summary, movers and droppedApps always cover the full top 200 regardless of `limit`; movement is empty on the first request for a chart; a ~30 second budget with fallback to the newest stored chart plus `stale: true` and `measuredAt`. It also states the no-API-key free tier with per-IP daily limits, which is exactly the kind of operational context annotations cannot convey.

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?

Dense and front-loaded: the core capability leads, then caveats (limit scope, first-day movement, staleness, response size, auth tier) follow in short sequenced sentences. It is on the long side and the field-list parenthetical is cramped, but nearly every sentence carries decision-relevant information.

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

Completeness5/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 carries the return-shape burden and does it: it names the per-app fields, describes what movers and droppedApps contain, and explains the `stale`/`measuredAt` fallback signature. That is enough for an agent to call the tool and interpret the response without further documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: that `limit` truncates only the returned entries and not the summary/movers/droppedApps sets, and that `fields: "compact"` omits icon URLs and numeric ids. Category and country semantics are mostly restated from the schema, which keeps this from a 5.

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 gives a specific verb and resource ('Get a store top chart') and enumerates the dimensions that define it (free/paid/grossing, overall or by category) plus the payload (per-app rank delta, new entries, movers, dropped apps). It never names a sibling such as sonar_app_rankings, so the store-wide-chart-versus-single-app distinction is left implicit even though the scope language points the right way.

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?

'Use to see what's rising in a market or category' gives one positive use case, which is genuinely helpful framing. There is no when-not guidance, no mention of which sibling answers per-app ranking history or keyword ranking questions, and no prerequisites, so an agent must infer routing from the sibling names alone.

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

All sonar toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources