Skip to main content
Glama
Sign In

AppmanAi

by com.appmanai
OverviewDiscussionsAdmin

Top apps in a category chart

category_top_apps
Read-only

List the apps at the top of a category chart (top free, top grossing, top paid) in a country. Use it to see who leads a category; list_categories has the valid tags. 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>"
    },
    "name": "category_top_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoChart date, YYYY-MM-DD. Defaults to the latest.
limitNoHow many rows to return, up to 200.
storeYesWhich app store: "android" (Google Play) or "ios" (App Store).
countryYesTwo-letter ISO country code, e.g. "US", "GB", "DE".
categoryNoCategory tag from list_categories.
extendedNoReturn full app profiles instead of package ids and ranks.
show_diffNoInclude each app's movement since the previous chart.
sub_categoryNoChart inside the category: "topselling_free", "topgrossing", "topselling_paid" on Google Play; "top-free", "top-paid" on the App Store. list_categories has the valid tags.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly and openWorld, so the safety profile is covered. The description adds genuinely non-structured context: this call costs 5 credits, which materially affects agent decision-making. It does not disclose result size or pagination behavior, but the credit cost is a strong addition.

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 short sentences, front-loaded with the operation, with the usage hint and credit cost trailing. No filler or repetition.

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 an 8-parameter tool with no output schema, the description is thin: it does not explain the shape of results (rank + package id vs. full profiles), the interplay between category and sub_category, or how limit affects output. The credit cost and tag pointer help, but an agent still has gaps to close from the schema alone.

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, date, limit, sub_category and extended are all documented in the schema with enums and formats. The description only restates the chart-type notion and the list_categories pointer, both of which the schema already carries. Baseline 3 applies.

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?

Specific verb ('List') plus resource ('apps at the top of a category chart') and it enumerates the chart types (top free, top grossing, top paid) scoped to a country. It stops short of distinguishing itself from sibling chart tools like app_category_rankings or keyword_top_apps, so an agent must infer which chart tool to pick.

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?

'Use it to see who leads a category' gives a clear use context and points to list_categories for valid tags. It gives no exclusions or routing versus the many sibling ranking tools, which is the main gap.

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