OrgLines

Create trip

create_trip

Create a DRAFT road trip in the caller's active workspace. Provide a 'title', an 'origin' and 'destination' (place names — resolve them first with geocode_place if you want to pin exact coordinates), the number of 'days', an optional 'start_date' (YYYY-MM-DD) and a 'preferences' object (vehicle_type, route_type fastest|shortest|scenic, accommodation_type, budget_per_day EUR, max_hours_per_day, avoid_tolls/avoid_highways/avoid_ferries). The trip is created empty (no days yet) — call generate_trip to build the route. Additive and low-risk. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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": {
      "title": "<title>",
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "create_trip"
  }
}

Input Schema

Name	Required	Description	Default
`days`	No
`title`	Yes
`origin`	Yes
`start_date`	No
`destination`	Yes
`preferences`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes well beyond the annotations by disclosing the two-phase confirmation behavior (status='confirmation_required', action_id, plan_token) and that the resulting trip contains no days. 'Additive and low-risk' largely restates destructiveHint=false, which is the only redundant clause; the confirmation semantics are the genuinely valuable addition.

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 the core action and relevant details; the CONFIRMATION block is critical and easy to find. Slightly dense, with one clause ('Additive and low-risk') that duplicates annotation information and could be cut.

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?

No output schema exists, yet the description still describes the response shape (status/action_id/plan_token) and the empty-trip consequence, which is what an agent needs to chain calls. Minor gaps: the days bounds (1-60) and whether the preferences list is exhaustive are not stated.

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

Parameters5/5

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

Schema description coverage is 0% and preferences is an untyped nested object, so the description carries the full burden — it enumerates the preference fields including the route_type enum (fastest|shortest|scenic), budget_per_day in EUR, and the avoid_tolls/highways/ferries flags, plus the YYYY-MM-DD date format and that origin/destination are place names, not coordinates.

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+resource+scope: 'Create a DRAFT road trip in the caller's active workspace.' It also carves out the boundary against siblings by naming geocode_place (for coordinate resolution) and generate_trip (for building the route), so an agent can place this tool in the workflow without opening other schemas.

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?

States exactly what to supply (title, origin, destination, days, optional start_date and preferences), when to pre-call geocode_place, and what to call next because the trip is created empty. It also gives the mandatory follow-up path: the tool is proposed only, and the write happens after confirm_action.

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

All OrgLines tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?