Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

oldnavy_stores

Find nearby Old Navy, Gap, Banana Republic, or Athleta stores by zip code, city, or coordinates. Returns addresses, phone numbers, distance, and specialties.

Instructions

Find Old Navy, Gap, Banana Republic, or Athleta store locations. Searches physical store locations for one storefront by free-text search (zip code or city) and/or coordinates. Provide search, or both lat and lng. Select the storefront with the brand parameter (on for Old Navy, gap for Gap, br for Banana Republic, at for Athleta; defaults to on). Returns each nearby store's name, full address, phone number, coordinates, distance, and specialties (e.g. "In-Store Shopping", "Outlet"). This is location search only -- it does not report per-item, per-store stock levels; use oldnavy-product-availability for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude (must be given together with lng)
lngNoLongitude (must be given together with lat)
brandNoStorefront to search
searchNoZip code or city to search near

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / brand / enum
      Added value: +[
+  "on",
+  "gap",
+  "br",
+  "at"
+]
  2. Addedv1.14.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full disclosure burden. It clearly states this is a search operation, enumerates returned fields (name, address, phone, coordinates, distance, specialties), and explicitly limits scope by saying it 'does not report per-item, per-store stock levels.' It does not mention rate limits or auth, but for a read-only store locator the behavior is well disclosed.

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?

The description is well organized and front-loaded, with distinct sentences for purpose, parameters, output, and limitations. Minor redundancy exists ('Find ... store locations' followed by 'Searches physical store locations'), but no sentence is wasted.

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?

Despite having no output schema, the description enumerates the returned data fields and covers parameters, defaults, and the tool's boundary relative to a sibling. For a moderate-complexity locator tool, an agent has enough context to invoke it correctly; missing edge-case behavior (e.g., no-results handling) is a minor gap.

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 the baseline is 3. The description adds value beyond the schema by explaining the mutually exclusive search-or-coordinate usage ('Provide search, or both lat and lng') and mapping brand enum codes to brand names with a default.

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 specific verb and resource: 'Find Old Navy, Gap, Banana Republic, or Athleta store locations.' It names the sibling tool oldnavy-product-availability and differentiates itself by saying 'This is location search only,' making its role unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit invocation guidance: 'Provide search, or both lat and lng' and 'Select the storefront with the brand parameter,' including code mappings and the default. It also states when not to use it and directs the agent to oldnavy-product-availability for stock-level queries.

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