Skip to main content
Glama

Update activity

update_activity
Destructive

Update an existing activity's details, pricing, season, or waivers.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "activity_id": "<activity_id>"
    },
    "name": "update_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
end_dayNo
dive_typeNoRequired for diving activities.
end_monthNo
equipmentNoEquipment items for the activity.
is_activeNo
start_dayNo
ratio_noteNo
route_nameNo
activity_idYes
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
descriptionNo
food_statusNo
minimum_ageNo
price_centsNo
price_rulesNoBusy-time price adjustments for the activity.
price_tiersNoPer-person prices that depend on the number of participants.
start_monthNo
waiver_textNo
country_codeNo
food_entriesNo
meeting_timeNoLocal meeting time in HH:MM format.
needs_reviewNo
pricing_modeNo
pricing_unitNo
tax_rate_bpsNo
waiver_titleNo
duration_daysNo
offers_rentalNo
excluded_itemsNo
included_itemsNo
tiered_pricingNo
deposit_enabledNo
id_requirementsNo
maximum_depth_mNo
scheduling_modeNo
waiver_requiredNo
balance_due_daysNo
duration_minutesNo
max_participantsNo
meeting_latitudeNo
meeting_locationNo
min_participantsNo
nitrox_availableNo
price_from_centsNo
clients_per_guideNo
meeting_longitudeNo
prerequisite_modeNo
prerequisite_textNo
balance_due_triggerNo
deposit_percent_bpsNo
experience_requiredNo
accommodation_placesNo
accommodation_statusNo
required_specialtiesNo
requires_card_uploadNo
auto_cancel_below_minNo
cancellation_policy_idNo
departure_decision_daysNo
id_requirement_requiredNo
last_dive_within_monthsNo
requires_logbook_uploadNo
minimum_experience_levelNo
prerequisite_activity_idsNo
minimum_experience_durationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare a non-read-only, destructive operation, so the description is not the sole carrier of risk. Still, it adds nothing beyond them: with 65 fields and destructiveHint=true, an agent critically needs to know whether this is a partial merge (unspecified fields preserved) or a full replace (unspecified fields cleared), and the description is silent on this.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no waste, but at this scale the brevity reads as under-specification rather than economy; the sentence cannot carry the burden of a 65-parameter mutation tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 65 parameters, 9% schema coverage, no output schema, and a destructive annotation, the description is far too thin for an agent to invoke this safely or correctly. It identifies the resource but omits update semantics, required-vs-optional behavior, and any caution about overwriting activity configuration.

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 description coverage is only 9% across 65 parameters, so the description should compensate heavily. It only loosely buckets fields into "details, pricing, season, or waivers" without mapping them to anything an agent can act on, leaving the vast majority of parameters (nested price_rules, price_tiers, equipment, waiver fields, prerequisite_activity_ids) undefined in both schema and text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Update an existing activity") and names four content domains (details, pricing, season, waivers). It is clear enough to distinguish from create_activity/delete_activity by name, but it does not explicitly differentiate or route against siblings like update_departure or duplicate_activity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no guidance on when to use this versus alternatives, no preconditions (e.g., activity must exist, required permissions), and no mention of what to do for related edits covered by other tools such as update_departure or update_booking_meeting_location.

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