Your Next Tours

Set Trip Stop Status

set_trip_item_status

Destructive

Record the on-site status of a trip stop: planned | in_progress | done | cancelled | skipped. Params: id (trip uuid), itemId (uuid) + body { status }. Setting in_progress or done also marks every EARLIER stop that is still planned or in_progress as done (trip order: day, then time; stops without a time keep their place); their ids come back in autoCompletedItemIds. Setting planned reopens a stop without touching others. NO notification is sent (a stop cancellation announcement requires trips:announce).

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": {
      "id": "<id>",
      "itemId": "<itemId>",
      "body": "<body>"
    },
    "name": "set_trip_item_status"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes
`body`	Yes
`itemId`	Yes

Output Schema

Name	Required	Description
`id`	No
`kind`	No
`label`	No
`notes`	No
`status`	No
`tripId`	No
`actualAt`	No	ISO 8601 timestamp
`createdAt`	No	ISO 8601 timestamp
`dayNumber`	No
`imageUrls`	No
`sortOrder`	No
`startTime`	No
`templateId`	No
`durationMin`	No
`locationLat`	No
`locationLng`	No
`locationText`	No
`sourceItemId`	No
`headsetPolicy`	No
`autoCompletedItemIds`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026
- addedOutput schema / properties / autoCompletedItemIds
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```

Changed2 schema fields changedOct 3, 2026

changedOutput schema / properties / headsetPolicy / properties / groupThreshold / type

Previous value: -[
-  "number",
-  "string"
-]New value: +[
+  "number",
+  "string",
+  "null"
+]

changedOutput schema / properties / sortOrder / type

Previous value: -[
-  "number",
-  "string"
-]New value: +[
+  "number",
+  "string",
+  "null"
+]

First observedOct 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description explains exactly what that destruction is: setting in_progress/done auto-completes every earlier stop still planned or in_progress, with trip-order semantics (day, then time; time-less stops keep their place) and the affected ids returned in autoCompletedItemIds. It also discloses the non-destructive reopen path (planned) and the silent-notification behavior, which annotations cannot convey.

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?

Four tight sentences plus a parenthetical, front-loaded with the core action and followed by the cascade side effect, the reopen case, and the notification caveat in descending importance. No filler, and the parenthetical ordering rule earns its space by making the cascade predictable.

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?

For a three-parameter mutation with a nested body and an output schema, the description covers the action, the status domain, the cascade side effect and its return field, the reversal path, and the permission/notification constraint. An agent can call it correctly without opening the schema.

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 carry the load; it identifies id as the trip uuid, itemId as the stop uuid, and body as { status } with the full status vocabulary. This substantially compensates, though it does not clarify what itemId refers to beyond a bare uuid or whether a status reset to the same value is a no-op (relevant given idempotentHint=false).

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?

"Record the on-site status of a trip stop" gives a specific verb and resource, and the enumerated status vocabulary (planned | in_progress | done | cancelled | skipped) makes the tool unmistakable against siblings like update_trip_item or add_trip_item.

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?

The description clearly implies usage (marking a stop's progress on-site) and states the permission boundary: no notification is sent, and a cancellation announcement requires trips:announce. It never explicitly contrasts against update_trip_item, so the agent must infer which tool to use for editing stop content versus status.

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

All Your Next Tours 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?