Crawlora MCP

ulta_stores

Read-only

Find nearby Ulta Beauty physical stores: name, phone, full address, hours, services, and coordinates. Either search, or both lat and lng, is required. search is a free-text zip code, city, or address, resolved to coordinates first; if it does not resolve to any location, a well-formed empty result is returned rather than an error. lat and lng, when given directly, skip that resolution step. radius_meters is optional (1000 to 50000, defaults to 25000). A location with no stores within the radius returns a well-formed empty result rather than an error.

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": "ulta_stores"
  }
}

Input Schema

Name	Required	Description
`lat`	No	Latitude, requires lng
`lng`	No	Longitude, requires lat
`search`	No	Free-text zip code, city, or address to resolve to coordinates
`radius_meters`	No	Search radius in meters, 1000 to 50000, defaults to 25000

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.

Changed4 schema fields changedOct 7, 2026
- addedInput schema / properties / lat / description
```
Added value: +"Latitude, requires lng"
```
- addedInput schema / properties / lng / description
```
Added value: +"Longitude, requires lat"
```
- addedInput schema / properties / radius_meters / description
```
Added value: +"Search radius in meters, 1000 to 50000, defaults to 25000"
```
- addedInput schema / properties / search / description
```
Added value: +"Free-text zip code, city, or address to resolve to coordinates"
```
First observedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral detail: an unresolved 'search' or a location with no stores within radius returns a well-formed empty result rather than an error — an important edge case an agent would otherwise have to guess. It stops short of rate-limit or pagination details.

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?

Purpose and returned fields are front-loaded, followed by the invocation rules and edge cases in logical order. It is slightly long, but each sentence carries information an agent needs, so little is wasted.

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 covering return values and annotations covering the safety profile, the description supplies the remaining essentials: required input combinations, resolution semantics, and graceful-empty-result behavior. 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 the baseline is 3. The description exceeds that by explaining the resolution behavior of 'search' (free-text zip/city/address resolved to coordinates first) and that lat/lng skip that step, plus the radius range and default, adding meaning beyond the schema's terse property descriptions.

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 nearby Ulta Beauty physical stores') and enumerates exactly what is returned (name, phone, address, hours, services, coordinates). An agent can immediately distinguish this from siblings like ulta_product, ulta_search, or ulta_category.

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?

It clearly states the invocation contract — either 'search', or both 'lat' and 'lng' is required — and explains the two input modes and how each behaves. It lacks explicit when-not-to-use guidance or named alternatives, but there is no competing Ulta store tool to route against.

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.