Skip to main content
Glama

Aisle

by wedding.aisle
OverviewDiscussionsAdmin

Remove Empty Place

remove_my_place
DestructiveIdempotent

Removes one or several identified empty places from the selected wedding and its property order, and returns the order that remains. The places list supplies their ids. With several, each place is removed or kept on its own, and the result lists which were removed and which kept, with the reason. A dry run reports the same without removing anything. This removes any recommendation or booking link on a removed place. Any rooms, including archived history, prevent removal. No rooms or payments are deleted. Requires sign-in and an Aisle membership.

Input Schema

NameRequiredDescriptionDefault
dry_runNoWhen true, reports which of the named places would be removed and which kept, with reasons, and removes nothing. Defaults to false.
place_idNoIdentifier of the empty property to remove, from the selected wedding’s places list. Provide this or place_ids.
place_idsNoIdentifiers of several empty properties to remove, from the selected wedding’s places list. Only these are considered. Provide this or place_id.
wedding_idNoIdentifier of a wedding the signed-in account can manage. Required when the account has multiple weddings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / dry_run
      Added value: +{
+  "description": "When true, reports which of the named places would be removed and which kept, with reasons, and removes nothing. Defaults to false.",
+  "type": "boolean"
+}
    • changedInput schema / properties / place_id / description
      Previous value: -"Identifier of the empty property to remove, from the selected wedding’s places list."New value: +"Identifier of the empty property to remove, from the selected wedding’s places list. Provide this or place_ids."
    • addedInput schema / properties / place_ids
      Added value: +{
+  "description": "Identifiers of several empty properties to remove, from the selected wedding’s places list. Only these are considered. Provide this or place_id.",
+  "items": {
+    "format": "uuid",
+    "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+    "type": "string"
+  },
+  "maxItems": 50,
+  "minItems": 1,
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "place_id"
-]
  2. Changed2 schema fields changed
    • addedInput schema / properties / place_id / format
      Added value: +"uuid"
    • addedInput schema / properties / place_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive/idempotent/open-world, and the description goes well beyond them: per-item partial success semantics ('each place is removed or kept on its own... with the reason'), dry-run behavior, side effects on recommendation/booking links, the safety guarantee that no rooms or payments are deleted, and explicit sign-in plus Aisle membership requirements.

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?

The core action and its precondition lead the text, and each sentence carries a distinct fact (multi-place semantics, dry run, side effects, blockers, auth). It is slightly long and repeats the dry-run/removal point across two sentences, costing it the top score.

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 no output schema, the description still describes the return shape (remaining order, per-place removed/kept with reasons) and covers auth, constraints, dry-run escape hatch, and mutation side effects. Nothing an agent needs to call it safely 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 coverage is 100%, so dry_run, place_id, place_ids and wedding_id are already fully documented in the schema. The description reinforces the sourcing of the ids and the dry-run meaning but adds no format, exclusivity, or batching detail beyond what the schema states, so the baseline 3 applies.

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 ('Removes ... empty places from the selected wedding and its property order') plus the scope restriction that only empty places qualify. The mention of returning 'the order that remains' distinguishes it from reorder_my_places and the other remove_my_* siblings, which touch different resources.

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?

Gives clear context: places come from the selected wedding's places list, dry_run previews without mutating, and 'any rooms, including archived history, prevent removal' defines the failure condition. It stops short of naming alternative tools (e.g. reorder_my_places) or explicitly stating when not to use it.

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

All Aisle toolsInspect
Try in Browser
Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources