Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_suggest

Fetch Microsoft Store autocomplete suggestions for a partial search term, returning text completions and matching product details like title, icon, and store URL.

Instructions

Get Microsoft Store search suggestions for a prefix. Returns typeahead-style Microsoft Store search suggestions for a partial search term: plain-text completions plus a short list of matching products (id, title, icon, department, and store URL). Credential-free public Microsoft Store data, read directly from the store's own autocomplete API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
localeNoDisplay locale (BCP-47)
prefixYesPartial search term to autocomplete
countryNoStore country/region code (ISO-2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral disclosure burden. It states the data is public, credential-free, read directly from Microsoft's own autocomplete API, and returns typeahead-style results. It does not cover rate limits or edge cases, but it gives meaningful operational context beyond the schema.

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 tightly written sentences front-load the core purpose and immediately describe the output. Every sentence contributes information about scope, return format, or data source, with no filler.

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?

The tool is simple, has only one required parameter, and has no output schema, so the description's explicit listing of returned product fields (id, title, icon, department, store URL) is essential and sufficient. It also communicates the credential-free nature, which is important for agent 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 coverage is 100%, so the schema already documents all three parameters. The description adds no new meaning for locale or country beyond the schema, and 'prefix' is described similarly in both places. This matches the baseline score of 3 for schema-heavy documentation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action ('get search suggestions'), a specific resource (Microsoft Store), and a clear precondition (a prefix / partial search term). It also states the exact return shape, which distinguishes it from full-search tools like microsoftstore_search.

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?

The description clearly implies typeahead/autocomplete use via 'for a prefix' and 'partial search term,' which distinguishes it from broader Microsoft Store search tools. It does not explicitly name alternatives or state when not to use it, but the context is clear enough for tool selection.

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