Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

shop_app_analysis

Analyze Shop.app query results. Returns a market snapshot derived from Shop.app search results, including price ranges, currencies, sale counts, discounts, and top shops. Limit defaults to 20 and accepts values up to 50.

Instructions

Analyze Shop.app query results. Returns a market snapshot derived from Shop.app search results, including price ranges, currencies, sale counts, discounts, and top shops. Limit defaults to 20 and accepts values up to 50.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum products to analyze, defaults to 20 and supports up to 50
queryYesSearch query
on_saleNoRequest sale products
in_stockNoRequest in-stock products
deep_searchNoAccepted for compatibility; Shop.app no longer offers a separate deep search mode, so results are unchanged

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / deep_search / description
      Previous value: -"Enable Shop.app deep search mode"New value: +"Accepted for compatibility; Shop.app no longer offers a separate deep search mode, so results are unchanged"
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

With no annotations and no output schema, the description carries the load and does so reasonably: it discloses the return shape ('price ranges, currencies, sale counts, discounts, and top shops') and the market-snapshot nature of the result. It omits auth/permission behavior, but for a read-style analysis endpoint the output disclosure is the valuable part.

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 sentences, front-loaded with purpose then output content, then the limit constraint. The final limit sentence is redundant with the schema but the overall structure is tight and wastes little.

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?

For an analysis tool with no annotations and no output schema, the description explains what the returned snapshot contains, which is the main missing piece it needed to cover. Only the lack of guidance against siblings and the deep_search no-op behavior keep it from fully complete.

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 five parameters including defaults and bounds. The description only restates the limit default/cap, which duplicates the schema, and adds nothing for query, on_sale, in_stock, or deep_search. Baseline 3.

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 ('Analyze Shop.app query results') and enumerates the derived outputs, so an agent knows this produces a market summary rather than raw listings. However, it never names the sibling it competes with (shop_app_search), so the boundary between analysis and search is left to inference.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of the alternative search tool. The phrase 'Analyze Shop.app query results' implies it operates on a query, but the agent gets no signal about when to prefer this over shop_app_search.

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