Skip to main content
Glama

Top charts

top_charts
Read-onlyIdempotent

Top free, paid or grossing chart for a store, country and category, with daily movement and new entries.

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>"
    },
    "name": "top_charts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows (default 100, max 200).
storeYesStore. Google Play needs GOOGLE_PLAY_SOURCE on the deployment.
countryYesTwo-letter ISO 3166 storefront code, e.g. US, GB (not UK), IN.
categoryNoCategory id from list_top_chart_categories (default overall).
languageNoBCP 47 language tag, e.g. en or pt-BR. Defaults to en.
collectionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / country / description
      Previous value: -"ISO country code, e.g. US, GB, IN."New value: +"Two-letter ISO 3166 storefront code, e.g. US, GB (not UK), IN."
    • addedInput schema / properties / country / maxLength
      Added value: +2
    • addedInput schema / properties / country / minLength
      Added value: +2
    • addedInput schema / properties / country / pattern
      Added value: +"^[A-Za-z]{2}$"
    • changedInput schema / properties / language / description
      Previous value: -"Language code, e.g. en. Defaults to en."New value: +"BCP 47 language tag, e.g. en or pt-BR. Defaults to en."
  2. First observed

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds useful return-content behavior, namely daily movement and new entries, but it does not mention auth or deployment requirements, rate limits, or other operational constraints.

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?

The description is a single front-loaded sentence with no wasted wording. Every phrase contributes to identifying the chart type, the dimensions, and the returned data.

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 read-only chart tool with no output schema, the description gives enough context to understand what kind of result comes back, including daily movement and new entries. However, it omits usage guidance, sibling routing, and the relationship to list_top_chart_categories, leaving gaps for correct invocation.

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 high at 83%, so the schema already carries most parameter semantics. The description restates the main chart dimensions and collection options but adds little beyond the schema, leaving details like limit, language, and category sourcing to the parameter descriptions.

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 states a specific resource: top free, paid, or grossing charts for a store, country, and category, and it adds that results include daily movement and new entries. It is clear what the tool returns, but it does not explicitly differentiate itself from siblings such as new_releases or list_top_chart_categories.

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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. The parameters imply a chart lookup, but an agent must infer when to use list_top_chart_categories for category ids and how this differs from new_releases.

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