Skip to main content
Glama

ExpenseBot

by io.github.TotesMagotes
OverviewDiscussionsAdmin

get_trip_suggestions

Read-only

Review trips from the engine behind Review Expenses Find. Default is high-confidence only; for the trip list set includeCandidates:true: real trips first (AI-reviewed order when available), second homes and regular spots grouped; page with offset while remaining > 0. Name a trip with destination (e.g. "Copenhagen"); mode:area with area lists every expense in a country or city. Show dates, recorded locations, count and uncertainty; locations are not travel or client proof. Copy exact selections to group_expenses with a user-chosen trip/client name and confirm:false, then request approval. Possible additions stay out unless the user includes them (includePossibleAdditions:true). Merge/deduplicate selections for one destination; separate destinations need separate confirmations. Preserve existing assignments, Personal and read-only rows. Never infer clients or countries from currency. clientEmail mode is read-only.

Input Schema

NameRequiredDescriptionDefault
areaNoCountry or city for mode area, e.g. "Denmark" or "Copenhagen, Denmark". Ambiguous places return candidates to ask about.
modeNoepisode (default): trips. area: every expense located in the area.
limitNoResult cap (default 3, max 10), not an exhaustive list; see remaining.
offsetNoSkip this many results to page through remaining trips.
refreshNoRecheck current recorded expenses for suggested trips; never change their tags.
dateRangeNoInclusive period to find overlapping trips; returns full trip membership, including boundary dates outside the period.
clientEmailNoAccepted client's account email (accountants only).
destinationNoTrip the user named, e.g. "Copenhagen". Several matches return them for clarification; never guess.
includeCandidatesNoDefault false: high-confidence only. True: also show uncertain candidates without saving recommendations or changing expenses.
includePossibleAdditionsNoDefault false. True only when the user explicitly asks to include the separate possible additions in the selection.

Output Schema

NameRequiredDescriptionDefault
countNo
messageNo
successYes
proposalsNoRead-only trip proposals; accepting one continues through group_expenses.
remainingNoMore matching trips available with a larger offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / clientEmail / description
      Previous value: -"Client account email. Accountants may use this only for an accepted ExpenseBot client."New value: +"Accepted client's account email (accountants only)."
  2. Changed11 schema fields changed
    • addedInput schema / properties / area
      Added value: +{
+  "description": "Country or city for mode area, e.g. \"Denmark\" or \"Copenhagen, Denmark\". Ambiguous places return candidates to ask about.",
+  "type": "string"
+}
    • addedInput schema / properties / dateRange
      Added value: +{
+  "additionalProperties": false,
+  "description": "Inclusive period to find overlapping trips; returns full trip membership, including boundary dates outside the period.",
+  "properties": {
+    "end": {
+      "description": "Inclusive YYYY-MM-DD.",
+      "type": "string"
+    },
+    "start": {
+      "description": "Inclusive YYYY-MM-DD.",
+      "type": "string"
+    },
+    "type": {
+      "description": "Explicit calendar-date bounds.",
+      "enum": [
+        "specific"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "start",
+    "end"
+  ],
+  "type": "object"
+}
    • addedInput schema / properties / destination
      Added value: +{
+  "description": "Trip the user named, e.g. \"Copenhagen\". Several matches return them for clarification; never guess.",
+  "type": "string"
+}
    • addedInput schema / properties / includeCandidates
      Added value: +{
+  "default": false,
+  "description": "Default false: high-confidence only. True: also show uncertain candidates without saving recommendations or changing expenses.",
+  "type": "boolean"
+}
    • addedInput schema / properties / includePossibleAdditions
      Added value: +{
+  "description": "Default false. True only when the user explicitly asks to include the separate possible additions in the selection.",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum high-confidence proposals to return (default 3)."New value: +"Result cap (default 3, max 10), not an exhaustive list; see remaining."
    • changedInput schema / properties / limit / maximum
      Previous value: -5New value: +10
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "episode (default): trips. area: every expense located in the area.",
+  "enum": [
+    "episode",
+    "area"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Skip this many results to page through remaining trips.",
+  "minimum": 0,
+  "type": "integer"
+}
    • addedInput schema / properties / refresh
      Added value: +{
+  "description": "Recheck current recorded expenses for suggested trips; never change their tags.",
+  "type": "boolean"
+}
    • addedOutput schema / properties / remaining
      Added value: +{
+  "description": "More matching trips available with a larger offset.",
+  "type": "integer"
+}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "message": {
+      "type": "string"
+    },
+    "proposals": {
+      "description": "Read-only trip proposals; accepting one continues through group_expenses.",
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "success": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}
  4. 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
  5. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses important behavioral constraints: locations are not travel or client proof, clientEmail mode is read-only, refresh never changes tags, candidates are not saved, and existing assignments/Personal/read-only rows must be preserved. These cautions materially reduce misuse risk.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense and runs many workflow, mode, caveat, and downstream-tool instructions together in one block. Most content is relevant, but the lack of separation and the packed semicolon clauses make it harder to scan than a well-structured description.

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?

For a 10-parameter tool with an output schema, the description covers the key modes, defaults, paging behavior, downstream grouping workflow, and important safety caveats. It is broadly complete, though the dense presentation leaves some operational details harder to extract than necessary.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines all parameters. The description still adds useful semantics for mode:area, includeCandidates, destination disambiguation, offset paging, includePossibleAdditions, and the read-only clientEmail mode, though it does not add much for limit, refresh, or dateRange beyond 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?

The description clearly identifies a retrieval/review tool for trip suggestions, including default high-confidence behavior and an area mode. It is more specific than the name alone, but the phrase 'engine behind Review Expenses Find' is awkward and the description does not sharply distinguish this from sibling search/list tools.

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 substantial conditional guidance: use includeCandidates:true for uncertain candidates, use destination when the user names a trip, use mode:area to list expenses in a country or city, and keep possible additions out unless explicitly included. It also names group_expenses as the downstream tool, but it does not directly state when to prefer this over sibling expense-search tools.

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