Your Next Tours

Update Trip

update_trip

DestructiveIdempotent

Update trip metadata. Params: id (uuid) + body { name, startDate, endDate (YYYY-MM-DD), maxParticipants (null = unlimited), timezone (IANA name, e.g. 'Europe/Istanbul'), weatherCardsEnabled (boolean, turns the trip's weather cards on or off), stableLiveCode (boolean, keeps the same live broadcast link and join code for the whole trip; the code itself is assigned by the server) }. startDate/endDate/maxParticipants/timezone accept null to clear. NO notification is sent to participants.

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>",
      "body": "<body>"
    },
    "name": "update_trip"
  }
}

Input Schema

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

Output Schema

Name	Required	Description
`id`	No
`name`	No
`status`	No
`endDate`	No
`guideId`	No
`joinCode`	No
`timezone`	No
`createdAt`	No	ISO 8601 timestamp
`joinToken`	No
`programId`	No
`startDate`	No
`updatedAt`	No	ISO 8601 timestamp
`cancelledAt`	No	ISO 8601 timestamp
`completedAt`	No	ISO 8601 timestamp
`liveJoinUrl`	No
`cancelReason`	No
`liveJoinCode`	No
`coverImageUrl`	No
`coverThumbUrl`	No
`organizationId`	No
`stableLiveCode`	No
`maxParticipants`	No
`changedNotifiedAt`	No	ISO 8601 timestamp
`weatherCardsEnabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 3, 2026
- addedInput schema / properties / body / properties / stableLiveCode
```
Added value: +{
+  "type": "boolean"
+}
```
- addedOutput schema / properties / liveJoinCode
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / liveJoinUrl
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / stableLiveCode
```
Added value: +{
+  "type": "boolean"
+}
```
First observedOct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, and the description adds real context beyond them: null clears startDate/endDate/maxParticipants/timezone, the live code is server-assigned, and no participant notification is sent. That side-effect disclosure is valuable for a mutation tool.

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 is front-loaded in the first sentence, followed by a dense but purposeful param block where every clause conveys distinct meaning. It is tight given the number of fields it must document.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile; combined with the thorough param documentation, an agent has nearly everything needed. Only the absence of sibling routing keeps it from a 5.

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%, so the description must carry the load, and it does: it documents every body field plus semantics the schema omits, e.g. maxParticipants null = unlimited, timezone must be an IANA name, date format YYYY-MM-DD, and which fields accept null to clear.

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+resource ('Update trip metadata'), and the word 'metadata' scopes it away from sibling update_trip_item, which edits trip items. It is clear what it does, though it never names the alternative tools explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance, and no reference to any of the many siblings (update_trip_item, publish_trip, delete_trip). The 'NO notification' line is a behavioral fact, not routing guidance.

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?