Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

microsoftstore_suggest

Get Microsoft Store typeahead search suggestions for a partial term, returning completions and matching products with IDs, titles, icons, departments, and store URLs.

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).

Input 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

A3.6/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 usefully discloses the return shape (plain-text completions plus matching products with id, title, icon, department, store URL), but says nothing about authentication, rate limits, ordering, or side effects.

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 sentences, front-loaded with the core purpose and followed by a compact return-value summary. Every clause earns its place with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description appropriately explains the returned fields. It is largely complete for a simple typeahead tool, though it omits guidance on when to prefer it over microsoftstore_search and says nothing about how locale/country affect results.

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%, so the schema already documents prefix, locale, and country. The description only reinforces that prefix is a partial search term and adds no syntax or formatting detail beyond the schema, matching the baseline for full schema coverage.

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 states a specific verb and resource ('Get Microsoft Store search suggestions') and scopes it to a 'prefix'. The terms 'suggestions' and 'typeahead-style' distinguish it from the sibling microsoftstore_search, which performs full searches.

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?

It implies usage via 'for a prefix' and 'partial search term', but gives no explicit when-to-use guidance and never names an alternative such as microsoftstore_search. No prerequisites or exclusions are stated.

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