Skip to main content
Glama

create_journey

Create an active journey from a route_id returned by optimize_route (requires auth).

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": {
      "route_id": "<route_id>"
    },
    "name": "create_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNo
route_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context: the journey is created in an *active* state (real-world effect begins immediately) and authentication is required. Remaining gaps are minor, e.g. whether repeated calls create duplicate journeys.

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?

A single front-loaded sentence with no filler; the action, input provenance and auth requirement all land in one pass.

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?

An output schema exists, so return values need not be explained, and the description covers the input source, auth, and the active-state side effect. For an open-world mutation tool it could say a little more about consequences or failure modes, but nothing essential is missing for correct invocation.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It usefully documents the provenance constraint on route_id (must come from optimize_route) — the single most important fact for filling that field correctly — and the "requires auth" note flags the role of api_key. It does not explain the accepted format of route_id or that api_key may be omitted.

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?

States a specific verb and resource ("Create an active journey") and pins the input to a route_id produced by optimize_route, which lets an agent tell it apart from the route-analysis siblings. It stops short of a clean five because it does not explicitly contrast with related mutating siblings such as reroute.

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?

The precondition "from a route_id returned by optimize_route" gives a clear upstream step in the workflow, which is real guidance. However, it never says when to choose this over alternatives like reroute or assess_journey_risk, nor any when-not-to-use conditions.

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.