Load a saved trip by trip_id from save_trip. Returns continue_url for website handoff with configuration restored.
| Name | Required | Description | Default |
|---|---|---|---|
| trip_id | Yes | trip_id returned by save_trip. |
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Legacy alias of continue_url. | |
| note | No | ||
| success | Yes | ||
| summary | No | ||
| trip_id | No | ||
| trip_url | No | ||
| continue_url | No | Shareable Extralingo URL that restores configuration. | |
| configuration | No |
Changes observed during successful MCP inspections.
Input schema / properties / trip_id / descriptionAdded value: +"trip_id returned by save_trip."Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "configuration": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "continue_url": {
+ "description": "Shareable Extralingo URL that restores configuration.",
+ "type": "string"
+ },
+ "note": {
+ "type": "string"
+ },
+ "success": {
+ "const": true
+ },
+ "summary": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "trip_id": {
+ "type": "string"
+ },
+ "trip_url": {
+ "type": "string"
+ },
+ "url": {
+ "description": "Legacy alias of continue_url.",
+ "type": "string"
+ }
+ },
+ "required": [
+ "success"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds real behavior beyond them: the call restores configuration and returns a continue_url for website handoff, telling the agent the result is a handoff artifact rather than raw data.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the action and key, with no filler. Every clause contributes either identification or return behavior.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given a rich annotation set and an existing output schema, the description needs only to identify the tool and its handoff behavior, which it does. It omits error behavior (e.g., unknown/expired trip_id), a minor gap for a simple one-parameter read tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is a single parameter with 100% schema coverage, so the schema already documents trip_id. The description reinforces its provenance ('from save_trip'), which is mild added value but does not change the baseline of 3 when the schema carries the semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb (Load) and resource (saved trip), identifies the keying parameter (trip_id) and its origin (from save_trip), which cleanly separates it from save_trip and the other trip-related siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It establishes the context for use — you call this after save_trip with the trip_id that save_trip produced — which routes the agent correctly. It gives no explicit when-not or alternatives, but the retrieval-after-save relationship is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.