Skip to main content
Glama

Create Trip

create_trip

Create a new, empty trip — the container everything else hangs off. This is step 1 of planning: create the trip, then create_variant for the dates, then add_destination, then the accommodation / transport / event options. Ask the user for a name if they have not given one. The free plan allows one active trip of the user's own at a time (status planning or ready; the example trip and trips they were only invited to do not count), so do not create throwaway test trips: check list_trips first and reuse an active one. If this returns 403 because the limit is reached, do not retry. Tell the user they can free the slot by finishing or cancelling their current trip (update_trip with status finished or cancelled; a trip can also be deleted in the app), or upgrade to Premium for unlimited trips, and ask which they want.

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": {
      "data": "<data>"
    },
    "name": "create_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesThe new trip's details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / data / properties / coverPhoto / anyOf
      Previous value: -[
      -  {
      -    "description": "URL of the cover photo.",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "description": "Always set this, so the trip doesn't show a blank card. Use a photo that fits the trip: one of northernlight, beach, mountain, town, snow, sea, road, jungle, desert, city, balaton, london, or a directly linkable http or https image the owner may use.",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / data / properties / budget
      Added value: +{
      +  "description": "What the owner wants to spend. Set it only when the owner has stated one; without it, no budget warnings appear.",
      +  "properties": {
      +    "amount": {
      +      "description": "The most the owner wants to spend, as a positive number.",
      +      "minimum": 0,
      +      "type": "number"
      +    },
      +    "appliesTo": {
      +      "description": "\"stay\" compares the budget with the accommodation cost alone, \"total\" with the whole trip.",
      +      "enum": [
      +        "stay",
      +        "total"
      +      ],
      +      "type": "string"
      +    },
      +    "currency": {
      +      "description": "Three-letter currency code (e.g. \"EUR\").",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "amount",
      +    "currency",
      +    "appliesTo"
      +  ],
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations cover the safety profile (non-read-only, non-destructive, non-idempotent, closed-world), and the description adds the business constraint they cannot: a free-plan limit of one active trip, definition of what counts toward it, and the 403 failure mode with an explicit 'do not retry' instruction. It also supplies the remediation paths (update_trip to finished/cancelled, deletion in the app, Premium upgrade) and asks the agent to confirm with the user.

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?

Front-loaded with purpose, then workflow, then constraints, then error handling — a logical order with no filler. The final sentence is long and chains three remediation options, but each clause carries actionable content an agent needs on a 403.

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 mutation tool with a nested-object schema and no output schema, everything needed to call it correctly is present: quota limits, the required pre-check, the failure branch, and the placement in the broader planning flow. Nothing material is left to inference.

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 100% and the nested budget and coverPhoto fields are documented in detail by the schema itself, so the baseline is 3. The description adds only one extra semantic note ('Ask the user for a name if they have not given one'), leaving budget and coverPhoto entirely to 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?

Opens with a specific verb and resource ('Create a new, empty trip') and immediately frames it as 'the container everything else hangs off', which distinguishes it from create_variant, add_destination, and update_trip. The 'step 1 of planning' framing tells an agent exactly where this sits in the sibling workflow.

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?

Explicitly sequences the tool: create_trip, then create_variant, then add_destination, then the option tools. It also states a precondition (check list_trips first and reuse an active trip) and a prohibition (do not create throwaway test trips), which is stronger guidance than most definitions provide.

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.