Crawlora MCP

jcrew_stores

Read-only

J.Crew or J.Crew Factory's full open-store directory: address, phone, coordinates, services, and weekly hours. site selects the storefront and accepts jcrew or factory; defaults to jcrew. Give lat and lng together to sort by distance from that point (each store's distance_miles is then populated); omit both for the upstream's own order.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "jcrew_stores"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Latitude to sort distance from (must be given together with lng)
`lng`	No	Longitude to sort distance from (must be given together with lat)
`site`	No	Storefront whose stores to return. Documented values: jcrew, factory.

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.

Changed3 schema fields changedOct 7, 2026

addedInput schema / properties / lat / description

Added value: +"Latitude to sort distance from (must be given together with lng)"

addedInput schema / properties / lng / description

Added value: +"Longitude to sort distance from (must be given together with lat)"

addedInput schema / properties / site / description

Added value: +"Storefront whose stores to return. Documented values: jcrew, factory."

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the default value of 'site', that supplying lat/lng populates each store's distance_miles, and that omitting them preserves the upstream's own ordering.

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?

Three dense sentences, front-loaded with what the tool returns, then parameters in order of importance (site, then lat/lng). No filler and every clause carries information.

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 the description need not explain return shapes, and it still summarizes record contents. For a three-parameter, all-optional read tool with annotations covering safety, nothing an agent needs to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the accepted values for 'site' plus its default of jcrew, and the observable consequence of pairing lat/lng (distance_miles populated, results sorted). It does not, however, add format or range detail for the coordinate parameters 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 and resource — the full open-store directory — and enumerates exactly what each record contains (address, phone, coordinates, services, weekly hours). An agent can immediately tell this apart from the sibling jcrew_product, jcrew_category and jcrew_search tools.

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?

Explains when each parameter applies: 'site' selects the storefront and defaults to jcrew, and lat/lng should be supplied together to sort by distance or omitted for upstream order. No sibling alternative is named, but there is no competing store-listing tool in the jcrew toolset, so the context is adequate.

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?