Skip to main content
Glama
Sign In

OrgLines

by com.orglines
OverviewDiscussionsAdmin

Get trip

get_trip
Read-only

Read one road trip by id from the caller's workspace — the full nested itinerary: each day's route summary (distance/driving hours and, when the routing engine is reachable, the real road geometry from Valhalla — NOT a straight line), overnight stop, and estimated cost, plus the trip's status, shareable URL and this month's generation fair-use usage. Read-only. Returns null when no such trip is visible to the caller (a wrong-owner id is indistinguishable from a missing one — it never leaks another workspace's trip).

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": {
      "trip_id": "<trip_id>"
    },
    "name": "get_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
trip_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

The annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds real value with the null-on-not-found contract, the deliberate indistinguishability of wrong-owner versus missing ids (no cross-workspace leakage), and the Valhalla geometry caveat when the routing engine is unreachable.

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?

The core action and scope are front-loaded and every clause carries information, so nothing is padding. The single em-dash-heavy sentence runs long and could be split to make the null-return contract scannable, which keeps it just below top marks.

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 must describe return values and it does so thoroughly, including nested itinerary contents, status, URL, and usage counters, plus the null case. For a one-parameter read tool this is everything an agent needs to invoke and interpret it.

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?

The single trip_id parameter has 0% schema description coverage, so the description has to carry meaning and only partly does: it conveys that the id is resolved against the caller's workspace and that a foreign id behaves like a missing one. It never states the id format, where the caller obtains it, or whether it is opaque.

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?

It states a specific verb and resource ('Read one road trip by id from the caller's workspace') and then enumerates the payload: day routes, overnight stops, cost, status, shareable URL, and fair-use usage. Nothing here reads like a tautology of the title, and the workspace scoping distinguishes it from a generic lookup.

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 one-id read context is implied clearly enough that an agent knows this is a fetch-one-by-identifier call. However, it never states when to prefer this over sibling operations such as logistics_get_trip or the list/search style tools, and gives no prerequisites for having a valid id.

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

All OrgLines toolsInspect
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