Skip to main content
Glama
Sign In

Hamptons Verified

by com.hamptonsverified
OverviewDiscussionsAdmin

Shops: the verified East End stores, and where each one is

find_shops
Read-onlyIdempotent

Verified East End shops: 86 stores across 15 hamlets on the South Fork, North Fork and Shelter Island, in these categories: fashion, jewelry, swimwear, activewear, kids, toys, home, books, beauty, consignment, accessories, general-store, florist, antiques. Each row carries the address read off the brand's own store page at sourceUrl, a cross-checked coordinate with coordSource recording what corroborated it, phone where one is published, and the one-line what the guide keeps. The guide holds no opening hours for any shop, so no row carries an open/closed state or an hours line. query matches the name, the brand, the category and what, so 'bookshop', 'toys', 'flowers' and 'The Wharf Shop' all resolve. With no arguments nothing is looked up and the answer lists the categories and towns covered. Returns up to 8. townScope reports how the place argument was read; townScope.recognized: false means the name matched no East End place, the rows array is empty, and didYouMean lists near matches where any exist.

Input Schema

NameRequiredDescriptionDefault
townNoA hamlet ('Sag Harbor', 'East Hampton') or a region ('the Hamptons', 'North Fork'), in the asker's own words.
queryNoWhat to look for, e.g. 'bookshop', 'toys', 'flowers', 'swimwear', 'gift', or a store's name ('The Wharf Shop').
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / query / description
      Previous value: -"What they want, e.g. 'bookshop', 'toys', 'flowers', 'swimwear', 'gift', or a store's name ('The Wharf Shop')."New value: +"What to look for, e.g. 'bookshop', 'toys', 'flowers', 'swimwear', 'gift', or a store's name ('The Wharf Shop')."
    • changedInput schema / properties / town / description
      Previous value: -"A hamlet ('Sag Harbor', 'East Hampton') or a region ('the Hamptons', 'North Fork'). Pass the asker's own words."New value: +"A hamlet ('Sag Harbor', 'East Hampton') or a region ('the Hamptons', 'North Fork'), in the asker's own words."
  2. Changed1 schema field changed
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "fashion",
-  "jewelry",
-  "swimwear",
-  "activewear",
-  "kids",
-  "toys",
-  "home",
-  "books",
-  "beauty",
-  "consignment",
-  "accessories",
-  "general-store",
-  "florist"
-]New value: +[
+  "fashion",
+  "jewelry",
+  "swimwear",
+  "activewear",
+  "kids",
+  "toys",
+  "home",
+  "books",
+  "beauty",
+  "consignment",
+  "accessories",
+  "general-store",
+  "florist",
+  "antiques"
+]
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world. The description adds genuinely non-derivable traits: no opening hours exist so no open/closed state is returned, results are capped at 8, unrecognized towns yield an empty rows array plus didYouMean, and townScope explains how the place argument was interpreted.

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?

Front-loaded with scope and coverage, then provenance, then lookup semantics, then return-shape and edge-case behavior. Dense but nearly every clause carries information; the one weak spot is that the block is a single run-on paragraph rather than segmented.

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?

With no output schema, the description must cover return values and does: row fields (sourceUrl, coordSource, phone, what), the 8-row cap, townScope, rows array and didYouMean. It does not describe the full response envelope or ordering of rows, but an agent has enough to call and interpret results correctly.

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 67%, and the description compensates well for the undocumented parts: it specifies that query matches name, brand, category and the `what` field, and that town accepts hamlets or regions in the asker's own words with townScope reporting the interpretation. The category enum is not re-explained beyond the schema, keeping it from a 5.

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 — verified East End shops (86 stores across 15 hamlets) — plus the exact categories and the fields each row carries. An agent can immediately tell this is a curated shop directory rather than a general place lookup like search_places or a lodging tool.

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 the query semantics ('bookshop', 'toys', 'flowers', 'The Wharf Shop' all resolve) and defines the no-argument behavior as a coverage summary, which tells the agent when a bare call is appropriate. It does not explicitly name alternatives or exclusions (e.g., when to prefer search_places), so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Hamptons Verified toolsInspect
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