Skip to main content
Glama

get_trip_suggestions

Read-only

Review trips from the Review Expenses Find engine. Default is high-confidence only; for the trip list set includeCandidates:true (real trips first, second homes and regular spots grouped); page with offset while remaining > 0. Name a trip by destination (e.g. Copenhagen); mode:area lists expenses 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trip_suggestions"
  }
}

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.
clientEmailNoAccountants: accepted client email 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
    • removedOutput schema / properties / proposals / items / additionalProperties
      Removed value: -true
  2. Changed1 schema field changed
    • changedInput schema / properties / clientEmail / description
      Previous value: -"Accepted client's account email (accountants only)."New value: +"Accountants: accepted client email only."
  3. 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)."
  4. 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"
      +}
  5. 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"
      +}
  6. 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
  7. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and destructiveHint false, so the safety profile is known; the description still adds substantive behavioral context: locations are not proof of travel or client work, existing assignments and Personal/read-only rows must be preserved, clients and countries must never be inferred from currency, and selections for one destination must be merged before a single confirmation. Those are non-obvious operational constraints an agent could not get from the annotations or schema.

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?

Every clause carries information, but it is delivered as one dense, semicolon-chained block with no visual structure, mixing purpose, paging, display rules, mutation handoff, and preservation constraints at the same level. It would read far better front-loaded with purpose and split into usage versus constraints. No filler sentences, but the packaging costs it.

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 read tool with a nested dateRange object and an output schema, the description covers the workflow from suggestion review through handoff to group_expenses, plus the main correctness traps (currency inference, preserving read-only rows, separate confirmations per destination). Return values are correctly left to the output schema. Minor gaps remain around refresh semantics and the clientEmail accountant path beyond 'read-only', which the schema alone carries.

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?

With 100% schema coverage the baseline is 3, but the description adds intent the schema does not: destination is a user-named trip (with a concrete example), includeCandidates changes the result set rather than just a flag, includePossibleAdditions requires explicit user request, and offset paging is tied to a 'remaining' signal. These are meaningful behavioral glosses on the parameters rather than restatements.

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 uses a specific verb and resource ('Review trips from the Review Expenses Find engine') and immediately clarifies scope: high-confidence trips by default, with includeCandidates for the broader list, and mode:area for location-based expense listing. It also separates itself from the write path by naming group_expenses as the mutation step. It loses a point only because the 'Review Expenses Find engine' framing is internal jargon rather than a plain statement of what the tool returns.

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?

It explicitly states the default behavior (high-confidence only), how to widen it (includeCandidates:true), how to page (offset while remaining > 0), how to switch modes (mode:area for country/city expense listing), and the exact condition for including possible additions (user must explicitly ask). It also routes the agent onward: copy exact selections to group_expenses with confirm:false, then request approval. That is a complete when/when-not/alternatives picture.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.