Skip to main content
Glama

Create activity

create_activity

Create an activity the guide offers, with pricing, meeting details, and season. The category must already be selected for the business.

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": {
      "main_service_code": "<main_service_code>",
      "name": "<name>",
      "description": "<description>",
      "duration_minutes": "<duration_minutes>",
      "min_participants": "<min_participants>",
      "max_participants": "<max_participants>",
      "price_cents": "<price_cents>",
      "pricing_unit": "<pricing_unit>",
      "meeting_location": "<meeting_location>"
    },
    "name": "create_activity"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
end_dayNo
dive_typeNoRequired for diving activities.
end_monthNo
equipmentNoEquipment items for the activity.
is_activeNo
start_dayNo
ratio_noteNo
route_nameNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
descriptionYes
food_statusNo
minimum_ageNo
price_centsYes
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_unitYes
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_minutesYes
max_participantsYes
meeting_latitudeNo
meeting_locationYes
min_participantsYes
nitrox_availableNo
price_from_centsNo
clients_per_guideNo
main_service_codeYesCategory code the activity belongs to, e.g. hiking.
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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is known. The description adds the useful prerequisite that the category must exist, but for a large creation tool it says little about side effects, defaults, or failure behavior.

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 description is two front-loaded sentences with no filler, and the prerequisite is placed clearly at the end. It is concise, though the phrase "with pricing, meeting details, and season" is vague and underspecified for such a complex schema.

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?

This is a high-complexity creation tool with 65 parameters and no output schema, yet the description only covers a high-level purpose and a category prerequisite. It omits required-field guidance, important defaults, option meanings, and alternatives that an agent would need to call it reliably.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 11% across 65 parameters, so the description needs to carry much more meaning. It only vaguely groups "pricing, meeting details, and season" and does not explain required fields such as name, description, duration_minutes, participant limits, price_cents, pricing_unit, or meeting_location.

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?

The description states a specific verb and resource: "Create an activity the guide offers." It adds scope with pricing, meeting details, and season, but does not explicitly distinguish this from siblings like create_activity_from_template 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 Guidelines3/5

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

It gives one concrete precondition: "The category must already be selected for the business." However, it does not explain when to use this tool versus create_activity_from_template or duplicate_activity, nor does it describe exclusions or alternatives.

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