Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_recommended

Fetch the Microsoft Store's default 'Recommended for you' shelf, matching pre-typing search suggestions. Accepts optional locale and country codes.

Instructions

Get the Microsoft Store's default recommendation shelf. Returns the store's default, query-less "Recommended for you" shelf -- the same recommendations the search box shows before a caller types anything. No query parameters beyond region/locale.

Input Schema

NameRequiredDescriptionDefault
localeNoDisplay locale (BCP-47)
countryNoStore country/region code (ISO-2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses a useful constraint (query-less, only region/locale scoping) but says nothing about pagination, rate limits, auth, or the shape/size of the returned shelf.

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?

Three tight sentences with the core purpose front-loaded and the scoping constraint last. Every sentence contributes; nothing is padded.

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?

With no output schema and no annotations, the description should ideally describe the return shape (e.g., list of app entries) and any pagination. It adequately explains what the shelf is but leaves return structure and behavior under-specified.

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 100% for the two optional params (locale, country), so the schema already documents them. The description only reinforces that no other query params exist and does not add format or syntax detail beyond the schema. Baseline 3 is appropriate.

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 (Get) and resource (default recommendation shelf), and explains what it returns: the query-less 'Recommended for you' shelf. It distinguishes itself conceptually from search/suggest tools ('before a caller types anything') but never names the sibling tools it differs from.

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 note 'No query parameters beyond region/locale' implies the use case is a query-less default feed, which indirectly tells an agent when to pick this over microsoftstore_search or microsoftstore_suggest. However, no explicit when-to-use or when-not-to-use guidance against the many other microsoftstore_* siblings (charts, editorial, spotlight) is given.

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