Skip to main content
Glama

Create Variant

create_variant

Add an alternative version of the trip — "Beach option" vs "Mountain option", or the same route on different dates. A trip needs at least one variant before it can hold destinations or options, so create one right after create_trip. Dates live on the variant: either exact start/end dates or a flexible window with min/max nights.

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

Input Schema

NameRequiredDescriptionDefault
dataYesThe new variant's name, dates and notes.
tripIdYesId of the trip, as returned by list_trips or get_trip.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / data / properties / participants / properties / children / items / properties / age / maximum
      Added value: +17
    • addedInput schema / properties / data / properties / participants / properties / children / items / properties / age / minimum
      Added value: +0
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent create, so the safety profile is covered. The description adds real domain behavior beyond that: variants are a prerequisite container for destinations/options, and dates are owned by the variant. It doesn't mention that repeat calls create additional variants or what the response contains, but that gap is smaller given the annotation coverage.

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

Conciseness5/5

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

Three sentences, each doing distinct work: what the tool creates, the prerequisite ordering, and the date model. Purpose is front-loaded and nothing is redundant padding.

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

Completeness4/5

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

For a nested-object create with no output schema, the description covers purpose, call ordering, and date semantics well enough to invoke correctly. It omits whether the new variant becomes the selected variant (relevant given the select_variant sibling) and what the call returns, which would round out the picture.

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 both parameters and the nested date/participant structures are documented in the schema itself. The description restates the exact-vs-flexible date split and the name examples, which the schema already provides, and adds no format or validation detail (e.g. minNights/maxNights interaction) beyond it. Baseline 3 is appropriate.

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 ("Add an alternative version of the trip") and concretizes it with examples that map directly to the schema's name field. It distinguishes the concept from what lives on a variant (destinations, options) and positions itself relative to create_trip, so an agent can tell what this tool does versus its siblings.

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?

Explicitly says when to call it: "a trip needs at least one variant before it can hold destinations or options, so create one right after create_trip." That is a clear ordering rule an agent can act on. It doesn't name alternatives such as duplicate_variant for cloning an existing variant or update_variant for edits, so it stops just short of full routing guidance.

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.