Crawlora MCP

tiffany_stores

Read-only

Tiffany & Co. physical stores, boutiques, and cafes near a coordinate, ordered by distance -- address, phone, opening hours, in-store services and specialities, and live open/closed status.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "tiffany_stores"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional, 1 to 50, defaults to 10.
`radius`	No	Optional, 1 to 500 miles, defaults to 50.
`latitude`	Yes	Required. Latitude, -90 to 90.
`longitude`	Yes	Required. Longitude, -180 to 180.

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.

First observedOct 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real behavioral value by disclosing that results are distance-ordered and include a live open/closed status, which the annotations do not convey.

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?

A single front-loaded sentence with zero filler: resource, proximity scope, ordering, and returned fields, all in one pass.

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?

For a read-only store locator with an output schema present, the description covers the essential 'what and where' plus ordering. It is nearly complete; only explicit usage/alternative guidance is missing.

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 description coverage is 100%, so latitude/longitude/limit/radius (including their ranges and defaults) are fully documented in the schema. The description adds only the implied coordinate semantics and nothing about the radius/limit controls beyond what the schema already states.

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 resource (Tiffany & Co. physical stores, boutiques, and cafes) with a clear locating action (near a coordinate, ordered by distance), and enumerates the returned fields. An agent can distinguish this from tiffany_search/tiffany_product siblings without opening the schema.

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

Usage Guidelines3/5

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

The 'near a coordinate' phrasing implies the use case (proximity lookup), but there is no explicit when-to-use guidance, no mention of prerequisites, and no reference to an alternative tool. Usage is inferable but not spelled out.

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.