Mahonia

Add rows to a list

add_items

Adds rows to an existing list. Takes the list's edit link and the rows; each row may name a folder, and a folder that doesn't exist yet is created.

Input Schema

TableJSON Schema

Name	Required	Description
`again`	No	A call identical to one made in the last ten minutes is taken as a retry and adds nothing: the earlier result comes back with repeated set. Pass true to add the same rows a second time on purpose.
`items`	Yes
`folder`	No	A folder name for every row that doesn't name its own.
`edit_link`	Yes	The list's edit link, whole (mahonia.app/e/CODE#token). The part after # is the write capability.

Output Schema

TableJSON Schema

Name	Required	Description
`added`	Yes	Rows added.
`totals`	Yes	Whole grams, summed over every row of the list.
`repeated`	Yes	True when this call repeated one made in the last ten minutes: nothing was added again, and the figures are that call's. Pass again: true to add the rows a second time.
`share_link`	Yes
`folders_made`	Yes	Folders that didn't exist and were made for these rows.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 13, 2026

addedInput schema / properties / items / items / properties / needs_cooking

Added value: +{
+  "description": "Food to cook on this trip. Each unit assumes one boil for a rough fuel estimate; no quantity or weight changes.",
+  "type": "boolean"
+}

Changed1 schema field changedSep 13, 2026
- addedInput schema / properties / items / items / properties / name / minLength
```
Added value: +1
```

Changed3 schema fields changedSep 12, 2026

addedInput schema / properties / again

Added value: +{
+  "description": "A call identical to one made in the last ten minutes is taken as a retry and adds nothing: the earlier result comes back with repeated set. Pass true to add the same rows a second time on purpose.",
+  "type": "boolean"
+}

addedOutput schema / properties / repeated

Added value: +{
+  "description": "True when this call repeated one made in the last ten minutes: nothing was added again, and the figures are that call's. Pass again: true to add the rows a second time.",
+  "type": "boolean"
+}

changedOutput schema / required

Previous value: -[
-  "added",
-  "folders_made",
-  "share_link",
-  "totals"
-]New value: +[
+  "added",
+  "folders_made",
+  "share_link",
+  "totals",
+  "repeated"
+]

Changed1 schema field changedSep 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "added": {
+      "description": "Rows added.",
+      "type": "integer"
+    },
+    "folders_made": {
+      "description": "Folders that didn't exist and were made for these rows.",
+      "items": {
+        "description": "User text.",
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "share_link": {
+      "type": "string"
+    },
+    "totals": {
+      "description": "Whole grams, summed over every row of the list.",
+      "properties": {
+        "base_g": {
+          "description": "In the pack, consumables aside.",
+          "type": "integer"
+        },
+        "carried_g": {
+          "description": "base_g plus consumable_g: what is on your back.",
+          "type": "integer"
+        },
+        "consumable_g": {
+          "description": "Food, fuel, water.",
+          "type": "integer"
+        },
+        "item_count": {
+          "description": "Rows, nested ones included.",
+          "type": "integer"
+        },
+        "kcal": {
+          "description": "Only when a food row carries calories.",
+          "type": "number"
+        },
+        "total_g": {
+          "description": "carried_g plus worn_g.",
+          "type": "integer"
+        },
+        "worn_g": {
+          "description": "On your body.",
+          "type": "integer"
+        }
+      },
+      "required": [
+        "base_g",
+        "worn_g",
+        "consumable_g",
+        "carried_g",
+        "total_g",
+        "item_count"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "added",
+    "folders_made",
+    "share_link",
+    "totals"
+  ],
+  "type": "object"
+}

First observedSep 12, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive, closed-world. The description adds one trait beyond them: a folder that doesn't exist yet is created as a side effect. It does not mention the retry/duplicate-suppression behavior ("again") that the schema documents, nor permission/auth requirements.

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?

Two short sentences with no filler; the core action is front-loaded and the folder side effect follows. Every clause carries information, though the second sentence is slightly run-on.

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 not be explained, and the schema itself is highly detailed for the fields. The description covers the key write-side effect (folder creation) but omits any mention of retry semantics or list prerequisites, leaving a minor gap.

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%, so most parameters are already well documented in the schema. The description only restates the edit-link and folder semantics at a high level and adds no syntax or format detail beyond what the schema provides, so a baseline score is appropriate.

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 and resource ("Adds rows to an existing list") and even summarizes the required inputs (edit link + rows). It is clearly distinct from create_list and get_list, though it doesn't explicitly name those siblings to sharpen the boundary.

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?

The phrase "an existing list" implies a list must already exist, and the description names the edit link and rows as inputs, so usage is implied. But there is no explicit when-to-use, when-not-to-use, or pointer to create_list for lists that don't exist yet.

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.