Skip to main content
Glama

ExpenseBot

by io.github.TotesMagotes
OverviewDiscussionsAdmin

get_mileage_summary

Read-only

Mileage analytics — totals, breakdowns by month / client / purpose / category, plus deduction framing (cents-per-mile or cents-per-km × distance, country-aware IRS / CRA rates). Examples: 'mileage this year', 'miles driven for Acme', 'mileage by month', 'mileage deduction estimate', 'business miles last quarter'. Supports YoY / MoM / QoQ comparison phrasing. Returns: { message, data: { totalDistance, deductionEstimate?, breakdown?, comparison?, sampleMeta? } }.

Input Schema

NameRequiredDescriptionDefault
queryNoNatural language mileage question (e.g., 'mileage this year', 'miles driven for Acme client')
groupByNoHow to group the breakdown
dateRangeNoTime period filter; use exactly one variant matching the user's phrasing.

Output Schema

NameRequiredDescriptionDefault
dataNo
messageNo
successNoPresent only on the error branch (out of scope) / async path.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / dateRange / description
      Previous value: -"Time period filter. Use exactly one variant — pick the shape that matches the user's phrasing."New value: +"Time period filter; use exactly one variant matching the user's phrasing."
    • changedInput schema / properties / dateRange / oneOf
      Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "month": {
-        "description": "Month name or 1-12 (e.g., 'March' or '3')",
-        "type": "string"
-      },
-      "type": {
-        "const": "month",
-        "type": "string"
-      },
-      "year": {
-        "description": "4-digit year (e.g., 2026)",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "type",
-      "month",
-      "year"
-    ],
-    "title": "Specific month",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "quarter": {
-        "maximum": 4,
-        "minimum": 1,
-        "type": "integer"
-      },
-      "type": {
-        "const": "quarter",
-        "type": "string"
-      },
-      "year": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "type",
-      "quarter",
-      "year"
-    ],
-    "title": "Quarter of a year",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "type": {
-        "const": "year",
-        "type": "string"
-      },
-      "year": {
-        "type": "integer"
-      }
-    },
-    "required": [
-      "type",
-      "year"
-    ],
-    "title": "Full year",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "end": {
-        "description": "ISO date YYYY-MM-DD (inclusive)",
-        "format": "date",
-        "type": "string"
-      },
-      "start": {
-        "description": "ISO date YYYY-MM-DD (inclusive)",
-        "format": "date",
-        "type": "string"
-      },
-      "type": {
-        "const": "specific",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "start",
-      "end"
-    ],
-    "title": "Specific date range",
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "type": {
-        "const": "relative",
-        "type": "string"
-      },
-      "value": {
-        "description": "Relative range phrase, e.g., 'last month', 'YTD', 'this quarter', 'last 7 days'",
-        "type": "string"
-      }
-    },
-    "required": [
-      "type",
-      "value"
-    ],
-    "title": "Relative natural-language range",
-    "type": "object"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "month": {
+        "description": "Month name or 1-12 (e.g., 'March' or '3')",
+        "type": "string"
+      },
+      "type": {
+        "const": "month",
+        "type": "string"
+      },
+      "year": {
+        "description": "4-digit year (e.g., 2026)",
+        "type": "integer"
+      }
+    },
+    "required": [
+      "type",
+      "month",
+      "year"
+    ],
+    "title": "Specific month",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "quarter": {
+        "maximum": 4,
+        "minimum": 1,
+        "type": "integer"
+      },
+      "type": {
+        "const": "quarter",
+        "type": "string"
+      },
+      "year": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "type",
+      "quarter",
+      "year"
+    ],
+    "title": "Quarter of a year",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "year",
+        "type": "string"
+      },
+      "year": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "type",
+      "year"
+    ],
+    "title": "Full year",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "end": {
+        "description": "ISO date YYYY-MM-DD (inclusive)",
+        "format": "date",
+        "type": "string"
+      },
+      "start": {
+        "description": "ISO date YYYY-MM-DD (inclusive)",
+        "format": "date",
+        "type": "string"
+      },
+      "type": {
+        "const": "specific",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "start",
+      "end"
+    ],
+    "title": "Specific date range",
+    "type": "object"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "type": {
+        "const": "relative",
+        "type": "string"
+      },
+      "value": {
+        "description": "Relative phrase, e.g. 'last month', 'YTD', 'last 7 days'",
+        "type": "string"
+      }
+    },
+    "required": [
+      "type",
+      "value"
+    ],
+    "title": "Relative natural-language range",
+    "type": "object"
+  }
+]
    • changedOutput schema / description
      Previous value: -"Success returns message + data with the computed summary; success is not emitted on the inline analytics path."New value: +"Returns message + data; no success flag on the inline path."
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Success returns message + data with the computed summary; success is not emitted on the inline analytics path.",
+  "properties": {
+    "data": {
+      "additionalProperties": true,
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "success": {
+      "description": "Present only on the error branch (out of scope) / async path.",
+      "type": "boolean"
+    }
+  },
+  "required": [],
+  "type": "object"
+}
  3. Changed1 schema field changed
    • 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
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely useful behavioral context the annotations lack: deduction framing with country-aware IRS/CRA rates and cents-per-mile computation.

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?

Front-loads the core purpose ('Mileage analytics — totals, breakdowns...') before listing dimensions, deduction framing, examples and return shape. Dense but each clause carries information; the parenthetical rate explanation is slightly heavy but 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?

With an output schema, full schema coverage, and safe annotations, the description covers what an agent needs to call it and interpret results. The gap is minor: it doesn't clarify how free-text filtering (e.g. by client) interacts with groupBy.

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%, so parameters are well documented and the baseline is 3. The description's examples loosely map to the query parameter, but it also says breakdown 'by client' while the groupBy enum offers 'tag' rather than 'client', a minor mismatch that doesn't clarify over the schema.

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 ('Mileage analytics — totals, breakdowns') and enumerates the breakdown dimensions and deduction framing, so an agent knows exactly what it returns. It doesn't explicitly name competing siblings like get_spending_summary or get_income_summary to route away from them, keeping it just short of a 5.

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?

Provides concrete usage examples ('mileage this year', 'miles driven for Acme', 'business miles last quarter') and notes comparison phrasing support, giving clear context for when to reach for it. It never states when-not-to-use or the write alternative (add_mileage_entry), so no exclusions.

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

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