Extralingo

get_trip

Read-onlyIdempotent

Load a saved trip by trip_id from save_trip. Returns continue_url for website handoff with configuration restored.

Input Schema

Name	Required	Description	Default
`trip_id`	Yes	trip_id returned by save_trip.

Output Schema

Name	Required	Description
`url`	No	Legacy alias of continue_url.
`note`	No
`success`	Yes
`summary`	No	Human-readable configuration summary for agents.
`trip_id`	No	Shareable trip id (/s/{id}).
`trip_url`	No
`school_id`	No	Craft school entry id.
`school_url`	No
`school_name`	No
`continue_url`	No	Shareable Extralingo URL that restores configuration.
`configuration`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 3, 2026
- addedOutput schema / properties / school_id
```
Added value: +{
+  "description": "Craft school entry id.",
+  "type": "integer"
+}
```
- addedOutput schema / properties / school_name
```
Added value: +{
+  "type": "string"
+}
```
- addedOutput schema / properties / school_url
```
Added value: +{
+  "type": "string"
+}
```
- removedOutput schema / properties / summary / additionalProperties
```
Removed value: -true
```
- addedOutput schema / properties / summary / description
```
Added value: +"Human-readable configuration summary for agents."
```
- changedOutput schema / properties / summary / type
```
Previous value: -"object"New value: +"string"
```
- addedOutput schema / properties / trip_id / description
```
Added value: +"Shareable trip id (/s/{id})."
```

Changed2 schema fields changedOct 3, 2026

addedInput schema / properties / trip_id / description
```
Added value: +"trip_id returned by save_trip."
```

changedOutput 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"
+}

First observedOct 3, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuine context beyond them: the return payload is a continue_url intended for website handoff with configuration restored, telling the agent what the call actually yields and why.

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?

Two sentences, zero waste, with the primary action and its key output front-loaded. Every clause earns its place.

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-value documentation isn't strictly required, yet the description still flags the continue_url handoff, which is the practically important part. Nothing critical is missing for a one-param, read-only, idempotent retrieval tool.

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?

Schema coverage is 100% and the description's only parameter statement ("by trip_id") merely restates the schema's own "trip_id returned by save_trip." With a single well-documented parameter, baseline 3 applies; no added syntax or format detail.

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 ("Load") and resource ("saved trip") and ties it to the producing tool, save_trip, so an agent can distinguish it from the save_trip sibling. It stops short of differentiating itself from the other get_* siblings, but the pairing with save_trip makes the purpose unambiguous.

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?

"by trip_id from save_trip" implies the round-trip workflow (save first, then load), which is useful implied usage guidance. However there is no explicit when-to-use/when-not statement and no named alternative for a similar retrieval need.

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

All Extralingo 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?