Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jcrew_stores

Find J.Crew or J.Crew Factory store locations with addresses, phone numbers, coordinates, services, and weekly hours. Sort results by distance by providing latitude and longitude.

Instructions

Find J.Crew or J.Crew Factory store locations. Returns one storefront's full open-store directory (address, phone, coordinates, services, 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude to sort distance from (must be given together with lng)
lngNoLongitude to sort distance from (must be given together with lat)
siteNoStorefront whose stores to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / site / enum
      Added value: +[
+  "jcrew",
+  "factory"
+]
  2. Addedv1.16.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It reveals the output content (address, phone, coordinates, services, weekly hours), the sorting behavior (distance_miles populated when lat/lng given), and the default ordering (upstream's own order). This goes beyond simple read-only hints and gives the agent a concrete model of what will happen.

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?

The description is a compact three-sentence paragraph with no redundancy. It front-loads the core purpose, then adds parameter behavior and output details. Every sentence contributes new information, and the structure flows logically from what → how → output.

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?

Without an output schema, the description must explain return values, and it does: the directory includes address, phone, coordinates, services, and weekly hours. It also covers the distance_miles field and the default ordering. For a read-only store locator, this is complete and sufficient for an agent to call it correctly without further assumptions.

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 description coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the site default ('defaults to jcrew') and the purpose of lat/lng ('sort by distance from that point'), which the schema only states as 'must be given together.' This extra context helps an agent decide when to supply these coordinates, justifying a score above baseline.

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 opens with a clear, specific verb+resource: 'Find J.Crew or J.Crew Factory store locations.' It names the exact brand and distinguishes this tool from siblings like balenciaga_stores or ikea_stores. The purpose is unambiguous and does not rely on the tool name alone.

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 gives clear context on when to use the tool (for store locations) and explains parameter usage: site defaults, and lat/lng must be given together for distance sorting. However, it does not explicitly mention alternatives or when NOT to use this tool (e.g., for product info), so it lacks exclusions but provides adequate operational guidance.

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