Skip to main content
Glama

Handled Locator

by com.handledlocal
OverviewDiscussionsAdmin

Set a custom field across locations

set_custom_field
DestructiveIdempotent

Put the same extra field on many locations at once: a booking button, a social link, or a labelled fact like "Parking: street only". A value that is a URL becomes a clickable button; anything else shows as plain text. NOT for tags or categories, which are a different thing entirely: use tag_locations for those. Set remove to true to take the field off instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesThe field's name, shown as its label. For example "Book a table".
iconNoOptional glyph on the button.
colorNoHex colour for the button, for example "#C2540E". Ignored for plain text.
styleNoDefault filled. Outline uses the colour as border and text only.
valueNoThe field's value. A URL makes it a button, anything else shows as a labelled fact.
removeNoTake this field off the given locations instead of setting it.
locationIdsYesLocation ids to change. At most 200.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / icon / enum
      Previous value: -[
-  "store",
-  "shopping-bag",
-  "shopping-cart",
-  "coffee",
-  "utensils",
-  "wine",
-  "car",
-  "truck",
-  "package",
-  "fuel",
-  "circle-parking",
-  "wifi",
-  "clock",
-  "credit-card",
-  "accessibility",
-  "dog",
-  "baby",
-  "wrench",
-  "stethoscope",
-  "pill",
-  "dumbbell",
-  "building-2",
-  "warehouse",
-  "leaf",
-  "star"
-]New value: +[
+  "store",
+  "shopping-bag",
+  "shopping-cart",
+  "coffee",
+  "utensils",
+  "wine",
+  "car",
+  "truck",
+  "package",
+  "fuel",
+  "circle-parking",
+  "wifi",
+  "clock",
+  "calendar",
+  "credit-card",
+  "accessibility",
+  "dog",
+  "baby",
+  "wrench",
+  "stethoscope",
+  "pill",
+  "dumbbell",
+  "building-2",
+  "warehouse",
+  "leaf",
+  "star"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already signal a destructive, idempotent write operation, so the bar is lower. The description adds valuable behavioral detail beyond annotations: URL values become clickable buttons, non-URLs render as plain text, and remove toggles the operation from set to remove. This helps the agent anticipate side effects and rendering behavior.

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?

The description is compact and front-loaded: it states the core use case, gives examples, distinguishes from related tools, and covers the removal behavior in three sentences. Every sentence earns its place; there is no filler or repetition of schema content.

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?

Given 7 parameters, the schema covers all parameter details, and annotations cover safety traits, the description provides the essential operational context: batch behavior, value formatting, exclusions, and removal. It does not discuss return values, but there is no output schema and the tool is primarily an action, so this is not a significant 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 description coverage is 100%, so the schema already documents all parameters. The description still adds meaning by explaining the value semantics (URL vs plain text) and the remove flag's effect, with illustrative examples like 'Book a table' and 'Parking: street only'. This exceeds the baseline without duplicating the schema.

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 clearly states the action and resource: 'Put the same extra field on many locations at once' with concrete examples. It also explicitly differentiates from related functionality by saying 'NOT for tags or categories... use tag_locations for those', making the tool's scope 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 when-to-use guidance: for placing the same extra field across many locations, and explicitly excludes tags/categories with a pointer to the alternative tool. It also provides the conditional for removal: 'Set remove to true to take the field off instead.' This is direct, actionable routing guidance.

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