Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_charts

Fetch curated Microsoft Store app and game charts—top free, paid, grossing, trending, deals, new releases, or popular—filtered by category, country, or Game Pass.

Instructions

Get a curated Microsoft Store chart. Returns a curated Microsoft Store chart (top free, top paid, top grossing, trending, deals, new releases, getting-started picks, or -- apps only -- most popular), optionally scoped to a category/subcategory and, for games, by Xbox Game Pass availability or player count. Some charts (notably NewAndRising) can legitimately return fewer items than page_size even at the first page -- that reflects real sparsity for that chart.

Input Schema

NameRequiredDescriptionDefault
listYesChart to fetch
pageNo1-based page number
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)
categoryNoOptional category to scope the chart to further
page_sizeNoItems per page (max 24)
media_typeNoDepartment to scope the chart to
subcategoryNoOptional finer subcategory within category (apps only; requires category to also be set)
discount_filterNoOptional discount filter
num_players_filterNoOptional player-count filter (games only)
subscription_filterNoOptional subscription filter (games only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers a genuinely useful behavioral caveat: some charts (notably NewAndRising) can return fewer items than page_size even on page 1, which reflects real sparsity. Read-only nature is implied by "Get," but pagination defaults and locale/country behavior are left unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first two sentences restate the same idea ("Get a curated Microsoft Store chart" / "Returns a curated Microsoft Store chart"), wasting the front-loaded position before the useful chart enumeration. The final sparsity sentence and the filter clause do earn their place, keeping it adequate but not tight.

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?

For an 11-param chart tool with no output schema and no annotations, the description covers the chart vocabulary, scoping dimensions, game-specific filters, and a pagination edge case. Nothing an agent needs to call it correctly is obviously missing, and return-shape detail is not required absent an output schema.

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 meaning beyond the schema by mapping chart types to constraints ("apps only -- most popular") and clarifying that Game Pass and player-count filters apply to games. That mapping is not derivable from the raw enum descriptions alone.

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?

States a specific verb and resource ("Get a curated Microsoft Store chart") and enumerates the chart families it can return, so an agent knows exactly what this fetches. It never names or contrasts a sibling (e.g., microsoftstore_editorial or microsoftstore_category), so it stops short of the explicit differentiation a 5 requires.

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?

The description implies usage by listing scoping options (category/subcategory, Game Pass/player-count filters), which lets an agent infer when to apply them. It gives no explicit when-to-use versus alternatives and no prerequisites or exclusions, so guidance is only implied.

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

Deploy Server

Other Tools