Skip to main content
Glama

Handled Locator

by com.handledlocal
OverviewDiscussionsAdmin

Add a location

create_location

Add one location, or many in a single call. A plain address is geocoded automatically, so lat and lng are only needed to override the result. Pass locations with an array to add a batch: adding ten showrooms is one call, not ten, and the reply says exactly which ones landed. Counts against the plan's location allowance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude. Supplying lat and lng skips geocoding.
lngNoLongitude.
cityNo
nameNoBusiness or store name.
emailNo
hoursNoOpening hours keyed by ISO weekday, 1 = Monday. Each value is ONE {open, close} in 24h HH:MM, or null for closed — not a list, and a list is rejected. Example: {"1": {"open": "09:00", "close": "17:00"}, "7": null}. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch.
phoneNo
stateNo
addressNoFull address as a person would write it. Geocoded automatically unless lat and lng are supplied.
websiteNo
imageUrlNo
priorityNoHigher sorts first when there is no visitor position.
timezoneNoIANA timezone, for example America/Chicago.
locationsNoSeveral locations to add in one call (at most 50). Use this instead of the top-level fields when adding more than one; each entry takes the same fields.
hoursPatchNoChange only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {"7": {"open": "10:00", "close": "16:00"}} changes Sunday alone, and {"7": null} closes it. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent.
postalCodeNo
visibilityNohidden keeps the location in the account but off the public locator.
countryCodeNoTwo-letter ISO country code.
descriptionNo
markerColorNoHex colour for this location's map marker.
addressLine1NoStreet line, when the address is structured.
customFieldsNoExtra fields, keyed by the label shown to visitors. The value is either a plain string, or an object {value, color, icon, style} where `value` is the URL or text. There is no `label` or `url` key: the label is the key, and the URL goes in `value`. Example: {"Book a table": {"value": "https://example.com/book", "color": "#C2540E"}}. Never use this for tags or categories; use the categories field instead.
locationTypeNopoint is a physical address, service_area covers a radius, online is a stockist with no address.
onlineRegionsNoFor an online location: two-letter country codes it ships to or serves, e.g. ["us", "ca"]. Empty means every visitor sees it.
serviceRadiusKmNoRadius in km, for a service_area location.
serviceAreaCircleVisibleNoFor a service_area location: whether to draw its coverage circle. Null (the default) follows the locator's serviceAreaCircleVisible setting. False draws the pin without the circle.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / hours / description
      Previous value: -"Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."New value: +"Opening hours keyed by ISO weekday, 1 = Monday. Each value is ONE {open, close} in 24h HH:MM, or null for closed — not a list, and a list is rejected. Example: {\"1\": {\"open\": \"09:00\", \"close\": \"17:00\"}, \"7\": null}. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."
    • changedInput schema / properties / hoursPatch / description
      Previous value: -"Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": [{\"open\": \"10:00\", \"close\": \"16:00\"}]} changes Sunday alone. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent."New value: +"Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": {\"open\": \"10:00\", \"close\": \"16:00\"}} changes Sunday alone, and {\"7\": null} closes it. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent."
    • changedInput schema / properties / locations / items / properties / hours / description
      Previous value: -"Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."New value: +"Opening hours keyed by ISO weekday, 1 = Monday. Each value is ONE {open, close} in 24h HH:MM, or null for closed — not a list, and a list is rejected. Example: {\"1\": {\"open\": \"09:00\", \"close\": \"17:00\"}, \"7\": null}. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."
    • changedInput schema / properties / locations / items / properties / hoursPatch / description
      Previous value: -"Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": [{\"open\": \"10:00\", \"close\": \"16:00\"}]} changes Sunday alone. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent."New value: +"Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": {\"open\": \"10:00\", \"close\": \"16:00\"}} changes Sunday alone, and {\"7\": null} closes it. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent."
  2. Changed5 schema fields changed
    • changedInput schema / properties / hours / description
      Previous value: -"Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed."New value: +"Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch."
    • addedInput schema / properties / hoursPatch
      Added value: +{
+  "description": "Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": [{\"open\": \"10:00\", \"close\": \"16:00\"}]} changes Sunday alone. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent.",
+  "type": "object"
+}
    • addedInput schema / properties / locations
      Added value: +{
+  "description": "Several locations to add in one call (at most 50). Use this instead of the top-level fields when adding more than one; each entry takes the same fields.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "address": {
+        "description": "Full address as a person would write it. Geocoded automatically unless lat and lng are supplied.",
+        "type": "string"
+      },
+      "addressLine1": {
+        "description": "Street line, when the address is structured.",
+        "type": "string"
+      },
+      "city": {
+        "type": "string"
+      },
+      "countryCode": {
+        "description": "Two-letter ISO country code.",
+        "type": "string"
+      },
+      "customFields": {
+        "description": "Extra fields, keyed by the label shown to visitors. The value is either a plain string, or an object {value, color, icon, style} where `value` is the URL or text. There is no `label` or `url` key: the label is the key, and the URL goes in `value`. Example: {\"Book a table\": {\"value\": \"https://example.com/book\", \"color\": \"#C2540E\"}}. Never use this for tags or categories; use the categories field instead.",
+        "type": "object"
+      },
+      "description": {
+        "type": "string"
+      },
+      "email": {
+        "type": "string"
+      },
+      "hours": {
+        "description": "Opening hours keyed by ISO weekday, 1 = Monday. Each value is a list of {open, close} in 24h HH:MM, or null for closed. REPLACES the whole week: any day left out is cleared. To change one day without restating the rest, use hoursPatch.",
+        "type": "object"
+      },
+      "hoursPatch": {
+        "description": "Change only the days named, leaving every other day exactly as it is. Same shape as hours but partial: {\"7\": [{\"open\": \"10:00\", \"close\": \"16:00\"}]} changes Sunday alone. Use this to edit hours; it cannot silently revert a day you did not mention. Ignored if hours is also sent.",
+        "type": "object"
+      },
+      "imageUrl": {
+        "type": "string"
+      },
+      "lat": {
+        "description": "Latitude. Supplying lat and lng skips geocoding.",
+        "type": "number"
+      },
+      "lng": {
+        "description": "Longitude.",
+        "type": "number"
+      },
+      "locationType": {
+        "description": "point is a physical address, service_area covers a radius, online is a stockist with no address.",
+        "enum": [
+          "point",
+          "service_area",
+          "online"
+        ],
+        "type": "string"
+      },
+      "markerColor": {
+        "description": "Hex colour for this location's map marker.",
+        "type": "string"
+      },
+      "name": {
+        "description": "Business or store name.",
+        "type": "string"
+      },
+      "onlineRegions": {
+        "description": "For an online location: two-letter country codes it ships to or serves, e.g. [\"us\", \"ca\"]. Empty means every visitor sees it.",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "phone": {
+        "type": "string"
+      },
+      "postalCode": {
+        "type": "string"
+      },
+      "priority": {
+        "description": "Higher sorts first when there is no visitor position.",
+        "type": "number"
+      },
+      "serviceAreaCircleVisible": {
+        "description": "For a service_area location: whether to draw its coverage circle. Null (the default) follows the locator's serviceAreaCircleVisible setting. False draws the pin without the circle.",
+        "type": [
+          "boolean",
+          "null"
+        ]
+      },
+      "serviceRadiusKm": {
+        "description": "Radius in km, for a service_area location.",
+        "type": "number"
+      },
+      "state": {
+        "type": "string"
+      },
+      "timezone": {
+        "description": "IANA timezone, for example America/Chicago.",
+        "type": "string"
+      },
+      "visibility": {
+        "description": "hidden keeps the location in the account but off the public locator.",
+        "enum": [
+          "visible",
+          "hidden"
+        ],
+        "type": "string"
+      },
+      "website": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name"
+    ],
+    "type": "object"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
    • addedInput schema / properties / serviceAreaCircleVisible
      Added value: +{
+  "description": "For a service_area location: whether to draw its coverage circle. Null (the default) follows the locator's serviceAreaCircleVisible setting. False draws the pin without the circle.",
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
    • removedInput schema / required
      Removed value: -[
-  "name"
-]
  3. Changed1 schema field changed
    • addedInput schema / properties / onlineRegions
      Added value: +{
+  "description": "For an online location: two-letter country codes it ships to or serves, e.g. [\"us\", \"ca\"]. Empty means every visitor sees it.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: automatic geocoding, batch semantics, that the reply identifies which entries landed, and that the call consumes the plan's location allowance.

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?

Four tightly written sentences, front-loaded with the core action, then geocoding behavior, batch guidance, and the quota caveat. Every sentence carries distinct information and none is padding.

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 26-parameter tool with nested objects and no output schema, the description covers the key call-shaping decisions (single vs batch, geocoding override, quota impact). It omits return-shape detail beyond 'the reply says which ones landed', but the schema carries the field-level burden, so the coverage is nearly complete.

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 coverage is 69% and the schema itself is unusually rich, documenting hours/hoursPatch semantics, locationType, customFields shape, etc. The description's parameter notes (address geocoding, lat/lng override, the `locations` array for batching) largely restate what the schema already states, adding little meaning on top.

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 states a specific verb and resource ('Add one location, or many in a single call') and immediately clarifies the scope, single vs batch, which lets an agent distinguish it from update_location and delete_location 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 Guidelines4/5

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

It gives clear operational context: use the top-level fields for one location, pass `locations` as an array to add up to a batch, and supply lat/lng only to override geocoding. It stops short of naming the alternative siblings (e.g. update_location for edits), so no explicit exclusions.

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

All Handled Locator 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