Skip to main content
Glama

Tineo

by ai.tineo.api
OverviewDiscussionsAdmin

Assign traveler to itinerary item

traveler_assign
Idempotent

Assign one or more travelers to one or more segments in a single call. To put the same travelers on several segments (for example every flight of a trip), pass all of them in segment_ids and all travelers in traveler_ids in one call instead of one call per segment. Up to 50 segments and 50 travelers per call, and at most 200 segment-traveler pairs. Assigning an already-assigned traveler is a no-op, and each segment succeeds or fails on its own: the result lists what was assigned and, per segment, what failed and why.

Input Schema

NameRequiredDescriptionDefault
segment_idNoOne segment ID to assign travelers to. Use segment_ids for several.
segment_idsNoSegment IDs to assign the same travelers to, in one call.
traveler_idNoOne trip traveler ID to assign. Use traveler_ids for several.
traveler_idsNoTrip traveler IDs (from trip_travelers) to assign to every listed segment.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / segment_id / description
      Previous value: -"The segment ID to assign travelers to"New value: +"One segment ID to assign travelers to. Use segment_ids for several."
    • addedInput schema / properties / segment_ids
      Added value: +{
+  "description": "Segment IDs to assign the same travelers to, in one call.",
+  "items": {
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}
    • changedInput schema / properties / traveler_id / description
      Previous value: -"Single trip traveler ID to assign"New value: +"One trip traveler ID to assign. Use traveler_ids for several."
    • changedInput schema / properties / traveler_ids / description
      Previous value: -"Array of trip traveler IDs to assign (for batch assignment)"New value: +"Trip traveler IDs (from trip_travelers) to assign to every listed segment."
    • addedInput schema / properties / traveler_ids / maxItems
      Added value: +50
    • removedInput schema / required
      Removed value: -[
-  "segment_id"
-]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: idempotency behavior (already-assigned traveler is a no-op), partial-failure semantics (each segment succeeds or fails independently), and hard limits (50 segments, 50 travelers, 200 pairs). These are exactly the traits an agent needs to plan retries and error handling.

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?

Front-loads the core action, then the batching rationale, then limits and failure semantics. Three sentences, each carrying distinct, non-redundant information.

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?

With no output schema, the description compensates by describing the return shape (what was assigned, per-segment failures and why). Limits, idempotency, and failure model are all covered for a mutation tool.

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% and each parameter is already described in the schema, including the all-to-all pairing. The description only adds the 200 segment-traveler pair cap on top, so the baseline 3 holds.

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 (assign) plus both resources (travelers, segments) and the batch scope. An agent can distinguish it from siblings like travel_document_assign_trip and segment_associate_place without opening a schema.

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 tells the agent to use the plural arrays in one call rather than one call per segment, with a concrete example (every flight of a trip). Clear usage context, though it doesn't state any when-not-to-use case.

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

All Tineo toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources