Skip to main content
Glama

Edit an alert

update_alert
DestructiveIdempotent

Change an existing alert instead of replacing it. Dates, nights, notifications, party size, activity and equipment can all be edited, and the campground_selections can be NARROWED.

Prefer this over delete-and-recreate: an alert carries its scan history and accumulated odds, a recreate throws both away and leaves the user unwatched in between. Prefer it over a second alert too — every alert costs a slot against the tier limit and the 100-alert cap.

SELECTIONS ONLY NARROW. You may remove sites, zones or campgrounds; you may not add any, and you may not change the park. Quota is priced on what an alert watches, so an edit that grew a selection would route around the check that priced it. To watch MORE, create a second alert, or delete this one and create it again with the full list — and say which you did.

Omit a field to leave it alone; pass null to clear one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
alert_idYesThe alert's id, from list_my_alerts or create_alert.
date_endNoYYYY-MM-DD — the last bookable NIGHT.
pets_onlyNoOnly sites that allow pets.
tent_padsNoBackcountry ZONE inventory only (Parks Canada): how many tent pads the party needs. Ignored elsewhere.
date_startNoYYYY-MM-DD.
nights_maxNoLongest stay to accept, in nights; omit to accept any length from nights_min up.
nights_minNoShortest stay to accept, in nights.
notify_smsNoText message on a match. Pro tier only and silently dropped otherwise, needs a verified phone number, and it is the one channel that costs real money per send — it stays off unless the user has asked for texts.
party_sizeNoPeople in the party. Where inventory is per bed or per person (huts, some backcountry zones) an opening must fit this many.
split_stayNoAccept a stay split across DIFFERENT sites rather than one site for every night. More matches, at the cost of moving camp mid-trip.
days_filterNoWhich arrival days count: every day, weekends only, or weekdays only.
entry_datesNoENTRY-DATE inventory only: the exact dates wanted, YYYY-MM-DD. Replaces the current set, so pass every date you still want.
notify_pushNoSend a push notification to the account holder's phone when something opens.
is_tent_onlyNoOnly tent-only sites, for campers who want to avoid being pitched beside RVs. NOT the same as equipment_filter_mode 'tent'.
notify_emailNoPaid tiers only; silently dropped otherwise.
activity_typeNoThe activity the alert watches (as listed on the park: camping, backcountry, day_use, …).
is_accessibleNoOnly wheelchair-accessible sites.
has_electricityNoOnly sites with an electrical hookup.
is_pull_throughNoOnly pull-through sites (no reversing) — for big rigs.
sub_equipment_idNoFrom list_equipment_options for this park's provider. Never guess it: the integers are per-provider and a wrong one filters to the wrong sites silently.
campground_selectionsNoThe NARROWED selection — a strict subset of what the alert already watches. Anything not listed stops being watched.
equipment_filter_modeNoWhat the user is camping IN. 'any' watches every site regardless. Pair 'tent' or 'rv' with sub_equipment_id from list_equipment_options — the mode alone does not say WHICH trailer.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
park_idNo
user_idNo
date_endNo
providerNo
is_activeNo
park_nameNo
pets_onlyNo
tent_padsNo
alert_typeNo
created_atNo
date_startNo
nights_maxNo
nights_minNo
notify_smsNo
party_sizeNo
scan_countNo
shade_onlyNo
split_stayNo
updated_atNo
booking_urlNo
created_viaNo
days_filterNo
entry_datesNo
notify_pushNo
is_tent_onlyNo
notify_emailNo
activity_typeNo
day_use_cellsNo
is_accessibleNo
out_of_seasonNo
has_electricityNo
is_pull_throughNo
last_checked_atNo
waterfront_onlyNo
created_by_agentNo
last_notified_atNo
sub_equipment_idNo
notification_countNo
cancellations_foundNo
availabilities_foundNo
campground_selectionsNo
equipment_filter_modeNo
op_access_point_resource_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / activity_type / description
      Added value: +"The activity the alert watches (as listed on the park: camping, backcountry, day_use, …)."
    • addedInput schema / properties / alert_id / description
      Added value: +"The alert's id, from list_my_alerts or create_alert."
    • addedInput schema / properties / days_filter / description
      Added value: +"Which arrival days count: every day, weekends only, or weekdays only."
    • addedInput schema / properties / nights_max / description
      Added value: +"Longest stay to accept, in nights; omit to accept any length from nights_min up."
    • addedInput schema / properties / nights_min / description
      Added value: +"Shortest stay to accept, in nights."
    • addedInput schema / properties / notify_push / description
      Added value: +"Send a push notification to the account holder's phone when something opens."
    • addedInput schema / properties / party_size / description
      Added value: +"People in the party. Where inventory is per bed or per person (huts, some backcountry zones) an opening must fit this many."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description supplies the 'why': narrowing silently drops anything not listed, selections can only shrink so a growth edit would circumvent quota pricing, and SMS notifications cost real money and are silently dropped off-tier. It also states the omit-vs-null mutation contract, which is the core behavioral rule for a partial-update tool.

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?

Well front-loaded — purpose, then alternatives, then the narrowing constraint, then the omit/null rule — and every paragraph earns its place. It loses a point for mild repetition between the delete-and-recreate warning in paragraph two and the same remedy restated at the end of paragraph three.

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?

For a 22-parameter partial-update tool with an output schema (so return values need no explanation) and full schema coverage, the description covers the remaining unknowns: mutation semantics, the narrowing-only invariant, quota and slot side effects, and the cost/silent-drop behavior of notification channels. Nothing needed to call it correctly is missing.

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 baseline is 3 and the schema already carries field meanings. The description adds genuinely new semantics the schema lacks: the union-wide 'omit to leave alone, null to clear' rule and the hard constraint that campground_selections may only narrow and never change the park.

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 opening sentence gives a specific verb and resource ('change an existing alert'), and the 'instead of replacing it' qualifier immediately separates it from delete-and-recreate and from create_alert in the sibling set. The follow-on sentence enumerates the editable field families, so an agent knows the scope 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 Guidelines5/5

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

Explicit when-to-use against two named alternatives: prefer this over delete-and-recreate (preserves scan history and odds, avoids an unwatched gap) and over a second alert (slot and 100-alert cap costs). It also gives the correct escape hatch when the user needs MORE coverage — create a second alert or delete-and-recreate — closing the loop rather than leaving the agent stuck.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources