ExpenseBot

add_mileage_entry

Log a business mileage trip in ExpenseBot. Useful for realtors, consultants, contractors, and anyone who drives for work. Requires the user to have configured their mileage rate (cents/km or cents/mi) and unit (mi/km) in ExpenseBot Settings. The trip writes a row to their expense spreadsheet with the calculated dollar value. Use the Mileage and travel link from get_spreadsheet_url instead when the user needs Google Maps route calculation, mileage settings, repeated trips, calendar/rideshare import, per diem, or visual review.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Tag for client/project attribution (optional)
`city`	No	City (optional)
`date`	Yes	Trip date (YYYY-MM-DD). Required. Use the date the user gives; for "today" send today's calendar date in their timezone. If no date was given, ask.
`notes`	No	Optional user-supplied context stored with the mileage entry.
`purpose`	Yes	Business purpose / description of the trip (e.g., 'Client meeting at 1234 Main St')
`category`	No	Override the user's default mileage category (optional)
`distance`	Yes	Distance traveled in the user's configured unit (miles or km)
`roundTrip`	No	If true, doubles the distance (return trip)
`destination`	No	Destination address or location (optional)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	No
`message`	Yes
`success`	Yes
`settings`	No
`rowNumber`	No
`finalAnswer`	No
`spreadsheetUrl`	No
`responseGuidance`	No
`reviewExpensesUrl`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 2, 2026

changedInput schema / properties / date / description

Previous value: -"Trip date (YYYY-MM-DD). Defaults to today."New value: +"Trip date (YYYY-MM-DD). Required. Use the date the user gives; for \"today\" send today's calendar date in their timezone. If no date was given, ask."

changedInput schema / required

Previous value: -[
-  "distance",
-  "purpose"
-]New value: +[
+  "distance",
+  "purpose",
+  "date"
+]

Changed1 schema field changedSep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "finalAnswer": {
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "responseGuidance": {
+      "type": "string"
+    },
+    "reviewExpensesUrl": {
+      "type": "string"
+    },
+    "rowNumber": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "settings": {
+      "additionalProperties": true,
+      "properties": {
+        "allowancePerUnit": {
+          "type": "number"
+        },
+        "unit": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "spreadsheetUrl": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "message"
+  ],
+  "type": "object"
+}

Changed1 schema field changedAug 25, 2026

changedOutput schema / (root)

Previous value: -{
-  "additionalProperties": true,
-  "description": "Standard ExpenseBot tool result envelope. `message` is the human-readable summary the AI cites; `data` is the structured payload (totals, breakdowns, ids, etc.). On failure, `success` is false and `error` carries a code/message/hint triple.",
-  "properties": {
-    "data": {
-      "additionalProperties": true,
-      "description": "Structured payload. Shape varies per tool — common keys: total, breakdown, comparison, sampleMeta, ids, expenseId, reportId, signupUrl, results.",
-      "type": "object"
-    },
-    "error": {
-      "additionalProperties": true,
-      "description": "Present only when success === false.",
-      "properties": {
-        "code": {
-          "type": "string"
-        },
-        "hint": {
-          "type": "string"
-        },
-        "message": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "message": {
-      "description": "Human-readable result text. Always present on success; prefer rendering this verbatim before any further reasoning.",
-      "type": "string"
-    },
-    "sampleMeta": {
-      "additionalProperties": true,
-      "description": "Set when the underlying dataset was truncated. isTruncated=true means the agent saw a sample of `sampleCount` of `totalCount` rows; aggregate totals are still accurate.",
-      "properties": {
-        "isTruncated": {
-          "type": "boolean"
-        },
-        "sampleCount": {
-          "type": "integer"
-        },
-        "totalCount": {
-          "type": "integer"
-        }
-      },
-      "type": "object"
-    },
-    "success": {
-      "description": "False on tool errors; check before reading `data`.",
-      "type": "boolean"
-    }
-  },
-  "type": "object"
-}New value: +null

Changed1 schema field changedAug 22, 2026
- addedInput schema / properties / notes / description
```
Added value: +"Optional user-supplied context stored with the mileage entry."
```
First observedAug 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare the write safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds value beyond them: it discloses that a row is written to the user's expense spreadsheet with a calculated dollar value, and that mileage rate/unit settings must exist first. It does not cover duplicate handling or what happens if settings are missing.

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?

Four sentences, front-loaded with the action, then prerequisite, then side effect, then alternative. Each sentence earns its place, though the audience list ('realtors, consultants, contractors') is soft filler that could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 params, an output schema present, and annotations covering the safety profile, the description supplies exactly what structured fields cannot: the prerequisite configuration, the write side effect, and clear routing away from the sibling alternative. An agent has everything needed to invoke it correctly.

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 100%, so every parameter (including roundTrip's doubling behavior and the date timezone guidance) is already documented in the schema. The description only reinforces the unit dependency for `distance`; baseline 3 is appropriate when the schema carries the semantics.

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?

States a specific verb+resource ('Log a business mileage trip in ExpenseBot') and immediately contrasts it with the sibling route via get_spreadsheet_url. An agent can distinguish this write-tool from add_cash_expense, add_income, and get_trip_suggestions 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 Guidelines5/5

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

Gives an explicit prerequisite (user must have configured mileage rate and unit), a named alternative tool (`Mileage and travel link from get_spreadsheet_url`) and enumerates the exact conditions that select that alternative (Maps routing, repeated trips, calendar/rideshare import, per diem, visual review). Nothing is left to inference.

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

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