Mahonia

Set a list's title, dates, unit and trail

set_trip

DestructiveIdempotent

Sets any of a list's title, display unit, trip dates and trail on an existing list. Only the fields given change; an empty string clears a date or the trail. Takes the list's edit link.

Input Schema

TableJSON Schema

Name	Required	Description
`unit`	No	The unit the list displays in. Weights are in grams regardless.
`title`	No
`end_date`	No	YYYY-MM-DD, or an empty string to clear.
`edit_link`	Yes	The list's edit link, whole (mahonia.app/e/CODE#token). The part after # is the write capability.
`trail_url`	No	An http(s) link, or an empty string to clear the trail and everything that came with it (label, distance, climb, route).
`start_date`	No	YYYY-MM-DD, or an empty string to clear.
`trail_label`	No
`trail_distance_km`	No	Stored in metres and shown in the list's own distance unit.

Output Schema

TableJSON Schema

Name	Required	Description
`unit`	Yes	The unit the list displays in. Weights are in grams regardless.
`dates`	Yes
`title`	Yes	User text.
`trail`	Yes
`share_link`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 12, 2026

addedInput schema / properties / unit / description

Added value: +"The unit the list displays in. Weights are in grams regardless."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "dates": {
+      "properties": {
+        "end": {
+          "description": "YYYY-MM-DD.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "start": {
+          "description": "YYYY-MM-DD.",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "start",
+        "end"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "share_link": {
+      "type": "string"
+    },
+    "title": {
+      "description": "User text.",
+      "type": "string"
+    },
+    "trail": {
+      "properties": {
+        "ascent_m": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "descent_m": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "distance_m": {
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "label": {
+          "description": "User text.",
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "url": {
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "url",
+        "label",
+        "distance_m",
+        "ascent_m",
+        "descent_m"
+      ],
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "unit": {
+      "description": "The unit the list displays in. Weights are in grams regardless.",
+      "enum": [
+        "g",
+        "kg",
+        "oz",
+        "lb"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "title",
+    "unit",
+    "dates",
+    "trail",
+    "share_link"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With annotations already declaring destructiveHint=true and idempotentHint=true, the description adds real context beyond them: it explains that unspecified fields are left untouched and that an empty string clears a date or the trail. This directly discloses the destructive semantics of clearing rather than merely repeating the annotation.

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?

Three sentences, no filler, front-loaded with the set of mutable fields before the partial-update and clearing rules. Every sentence contributes an operative fact an agent needs.

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 values need no explanation, and the annotations cover the safety profile for this mutation. The description covers partial-update semantics and clearing, leaving only edge cases like invalid or expired edit links unaddressed.

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 description coverage is 75% and the schema already documents edit_link (with the # write capability), the empty-string clearing convention, and unit storage behavior. The description's 'Takes the list's edit link' and clearing rules largely restate what the schema provides, adding little syntax or format detail beyond it.

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?

The description states a specific verb (sets) plus resource (a list's fields) and enumerates exactly which fields are mutable: title, display unit, trip dates, and trail. The phrase 'on an existing list' implicitly separates it from create_list, so the agent can route between siblings without opening a schema.

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?

It gives clear operative context: 'Only the fields given change' defines the partial-update contract, and 'Takes the list's edit link' signals the prerequisite input. However, it never names an alternative tool or states when not to use this (e.g. versus create_list for a new list), so it stops short of explicit exclusion guidance.

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

All Mahonia 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.