Crawlora MCP

zara_stores

Read-only

Zara physical retail store locator: search nearby stores by latitude/longitude and radius, with each store's name, full address, phone, coordinates, opening hours status, pickup/donation eligibility, and store page URL. lat and lng are both required -- this endpoint does not accept a free-text zip/city search. A location with no nearby stores within the radius returns a well-formed empty result.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "zara_stores"
  }
}

Input Schema

Name	Required	Description
`lat`	Yes	Latitude
`lng`	Yes	Longitude
`radius`	No	Search radius in miles, 1 to 500, defaults to 30
`pickup_only`	No	Only return stores that support in-store pickup
`donation_only`	No	Only return stores that accept clothing donations

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 7, 2026
- addedInput schema / properties / donation_only / description
```
Added value: +"Only return stores that accept clothing donations"
```
- addedInput schema / properties / lat / description
```
Added value: +"Latitude"
```
- addedInput schema / properties / lng / description
```
Added value: +"Longitude"
```
- addedInput schema / properties / pickup_only / description
```
Added value: +"Only return stores that support in-store pickup"
```
- addedInput schema / properties / radius / description
```
Added value: +"Search radius in miles, 1 to 500, defaults to 30"
```
First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the read-only, open-world safety profile, so the bar is lower; the description still adds value by disclosing the returned field set and the empty-result behavior for out-of-range locations. It does not mention pagination, but none is implied.

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?

Front-loaded with the core purpose, then output fields, then the key constraint and edge case, in three tight sentences with no waste.

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?

With an output schema present, return values needn't be explained, yet the description still notes the important constraint and empty-result edge case. An agent has everything needed to call it correctly.

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 lat/lng/radius/pickup_only/donation_only are already documented. The description reinforces that coordinates (not text) are required, which is useful, but adds no syntax or format detail beyond the schema.

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?

States a specific verb+resource (locate Zara physical retail stores by coordinates) and enumerates the returned fields, making it clearly distinct from siblings like zara_search and zara_product which handle products.

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?

Explicitly states lat/lng are required and that free-text zip/city search is NOT supported, which steers invocation correctly. It gives the condition but does not name the sibling tool (e.g., a geocoding tool) an agent should use instead.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?