Skip to main content
Glama

add_mileage_entry

Log one user-confirmed business trip; writes on call, no server preview. Saved mode selects rate-based expense or distance-only trip; trackingMode overrides. For routes, vehicle setup/readings, imports or review, open Mileage and travel via get_spreadsheet_url.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "distance": "<distance>",
      "purpose": "<purpose>",
      "date": "<date>"
    },
    "name": "add_mileage_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoClient/project tag.
cityNoCity.
dateYesRequired YYYY-MM-DD. Use the given date; for today use the user's timezone. Ask if missing.
unitNoTrip-log unit; omit for saved. Expense uses configured unit.
notesNoUser context.
purposeYesBusiness trip purpose.
categoryNoMileage category override.
distanceYesDistance in configured miles/km.
roundTripNoDouble distance for return trip.
vehicleIdNoExisting vehicle ID; omit for unassigned; never invent.
destinationNoDestination.
operationIdNoStable ID required for trip_log; reuse for the same request; never repeat an unverified save.
trackingModeNoOptional override; otherwise saved mode. Never infer from country or occupation.

Output Schema

NameRequiredDescriptionDefault
dataNo
messageYes
successYes
settingsNo
rowNumberNo
finalAnswerNo
trackingModeNo
mileageLogUrlNo
spreadsheetUrlNo
responseGuidanceNo
reviewExpensesUrlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedOutput schema / properties / data / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / rowNumber / minimum
      Removed value: -1
    • removedOutput schema / properties / settings / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / settings / properties
      Removed value: -{
      -  "allowancePerUnit": {
      -    "type": "number"
      -  },
      -  "unit": {
      -    "type": "string"
      -  }
      -}
  2. Changed15 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Override the user's default mileage category (optional)"New value: +"Mileage category override."
    • changedInput schema / properties / city / description
      Previous value: -"City (optional)"New value: +"City."
    • changedInput schema / properties / date / description
      Previous 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."New value: +"Required YYYY-MM-DD. Use the given date; for today use the user's timezone. Ask if missing."
    • changedInput schema / properties / destination / description
      Previous value: -"Destination address or location (optional)"New value: +"Destination."
    • changedInput schema / properties / distance / description
      Previous value: -"Distance traveled in the user's configured unit (miles or km)"New value: +"Distance in configured miles/km."
    • changedInput schema / properties / notes / description
      Previous value: -"Optional user-supplied context stored with the mileage entry."New value: +"User context."
    • addedInput schema / properties / operationId
      Added value: +{
      +  "description": "Stable ID required for trip_log; reuse for the same request; never repeat an unverified save.",
      +  "type": "string"
      +}
    • changedInput schema / properties / purpose / description
      Previous value: -"Business purpose / description of the trip (e.g., 'Client meeting at 1234 Main St')"New value: +"Business trip purpose."
    • changedInput schema / properties / roundTrip / description
      Previous value: -"If true, doubles the distance (return trip)"New value: +"Double distance for return trip."
    • changedInput schema / properties / tag / description
      Previous value: -"Tag for client/project attribution (optional)"New value: +"Client/project tag."
    • addedInput schema / properties / trackingMode
      Added value: +{
      +  "description": "Optional override; otherwise saved mode. Never infer from country or occupation.",
      +  "enum": [
      +    "expense",
      +    "trip_log"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / unit
      Added value: +{
      +  "description": "Trip-log unit; omit for saved. Expense uses configured unit.",
      +  "enum": [
      +    "km",
      +    "mi"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / vehicleId
      Added value: +{
      +  "description": "Existing vehicle ID; omit for unassigned; never invent.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / mileageLogUrl
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / trackingMode
      Added value: +{
      +  "enum": [
      +    "expense",
      +    "trip_log"
      +  ],
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • 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"
      +]
  4. Changed1 schema field changed
    • 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"
      +}
  5. 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
  6. Changed1 schema field changed
    • addedInput schema / properties / notes / description
      Added value: +"Optional user-supplied context stored with the mileage entry."
  7. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description adds genuinely new behavioral context: the write happens immediately on call with no server-side preview or draft, so the agent must confirm with the user first. It does not discuss failure modes or what happens if a save partially fails, which is the remaining gap.

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 dense sentences, front-loaded with the action and the write-on-call warning, then the mode semantics, then the escape hatch to a sibling. The telegraphic phrasing ('vehicle setup/readings, imports or review') is compact but readable; nothing is padded.

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 13-parameter mutation tool with full schema coverage and an output schema, the description covers the decision-critical parts: that it writes immediately, how the record type is chosen, and where to go for adjacent tasks. Return values and per-field rules are already carried by the schema and output schema.

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 baseline is 3, but the description adds cross-parameter meaning the schema only hints at: the saved mode decides whether an expense or a distance-only trip is created, and trackingMode explicitly overrides it (and 'never infer from country or occupation' in the schema reinforces this). That mode-interaction is the single most consequential parameter behavior here.

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?

Names a specific verb and resource ('Log one user-confirmed business trip') and immediately bounds the scope with 'no server preview'. The second sentence distinguishes the two record shapes (rate-based expense vs distance-only trip) this call can produce, which an agent cannot infer from the name alone.

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?

Explicitly routes the agent away from this tool for adjacent work: 'For routes, vehicle setup/readings, imports or review, open Mileage and travel via get_spreadsheet_url.' It also states the precondition that the trip must be user-confirmed before calling, giving both a when and a when-not.

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.