Skip to main content
Glama

ExpenseBot

by io.github.TotesMagotes

create_client_invoice

Destructive

Create the exact invoice previously returned by prepare_client_invoice. This is a confirmed write: it revalidates the report snapshot and client identity, creates a private editable Google Doc plus private PDF and DOCX copies, records the issued invoice, and supersedes an older active invoice for the same report. It does not send email or create an Income row. If tax is positive, confirmTax must be true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmTaxNoTrue only after the user confirms the displayed tax label and rate.
operationIdNoOptional retry key. Reuse it after an uncertain response.
preparationIdYesShort-lived ID returned by prepare_client_invoice.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 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
  2. Changed16 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / advanceApplied
      Removed value: -{
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / billToEmail
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / clientAddress
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / clientName
      Removed value: -{
-  "description": "In in-app chat, the full client name shown on the invoice.",
-  "type": "string"
-}
    • removedInput schema / properties / customLineItems
      Removed value: -{
-  "items": {
-    "properties": {
-      "amount": {
-        "exclusiveMinimum": 0,
-        "type": "number"
-      },
-      "description": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "description",
-      "amount"
-    ],
-    "type": "object"
-  },
-  "maxItems": 25,
-  "type": "array"
-}
    • removedInput schema / properties / invoiceNumber
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / issueDate
      Removed value: -{
-  "description": "In in-app chat, a calendar-valid YYYY-MM-DD invoice date.",
-  "type": "string"
-}
    • removedInput schema / properties / markupPct
      Removed value: -{
-  "maximum": 100,
-  "minimum": 0,
-  "type": "number"
-}
    • removedInput schema / properties / mentionSupportingReceipts
      Removed value: -{
-  "type": "boolean"
-}
    • removedInput schema / properties / paymentTerms
      Removed value: -{
-  "enum": [
-    "due_on_receipt",
-    "net7",
-    "net14",
-    "net15",
-    "net30",
-    "net45",
-    "net60"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / receiptIds
      Removed value: -{
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / reportId
      Removed value: -{
-  "description": "In in-app chat, the saved report ID to prepare and confirm.",
-  "type": "string"
-}
    • removedInput schema / properties / taxLabel
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / taxPct
      Removed value: -{
-  "maximum": 100,
-  "minimum": 0,
-  "type": "number"
-}
    • addedInput schema / required
      Added value: +[
+  "preparationId"
+]
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

The description fully discloses side effects: revalidation, creation of Google Doc, PDF, and DOCX copies, recording the invoice, and superseding an older active invoice. This goes well beyond the destructiveHint and readOnlyHint annotations, since the agent learns exactly what state may change and what is intentionally not done.

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

Conciseness5/5

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

The description is dense and well-structured, starting with the core purpose and then covering prerequisites, side effects, exclusions, and a specific required condition. Every sentence adds operational value with no redundancy.

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?

For a write tool with no output schema and destructiveHint=true, this description gives the agent enough to call it safely: required ID source, confirmTax condition, external document creation, superseding behavior, and what it does not do. No critical call-time decision is left unexplained.

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 meaningful context: preparationId is short-lived, confirmTax is required when tax is positive, and operationId is for retry. The description strengthens understanding of the parameters beyond their plain schema definitions.

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?

The description clearly states it creates the exact invoice previously produced by prepare_client_invoice, identifies it as a confirmed write, and lists the concrete artifacts it produces. This makes it easy to distinguish from prepare_client_invoice, mark_client_invoice_paid, and add_income 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 explicitly ties usage to an invoice prepared via prepare_client_invoice and specifies that tax confirmation is required when tax is positive. It also lists what it does not do, excluding email and Income row creation, though it does not explicitly name the alternatives an agent should use for those actions.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation3/5

Most tools are explicitly scoped, but several analytics/retrieval tools overlap in purpose, such as get_spending_summary vs get_deep_analytics vs get_monthly_books_review, and generic search vs search_expenses vs search_knowledge. The detailed descriptions help, but an agent still has to carefully choose between near-equivalent options like correct_expenses vs update_expense and the three add_income variants.

Naming Consistency5/5

Tool names consistently use lower_snake_case with a recognizable verb prefix: get_*, list_*, add_*, create_*, check_*, scan_*, search_*, and whatif_*. Minor exceptions like fetch and search are still terse retrieval verbs rather than a different naming style, so the overall pattern is predictable.

Tool Count1/5

With 59 tools, this exceeds the 50+ threshold for an extreme tool count and creates a heavy selection surface for an agent. Even though ExpenseBot covers many subdomains, many get_/list_/add_ variants could be consolidated into fewer parameterized tools. The count undermines the otherwise clear naming structure.

Completeness3/5

The surface is strong for creating, reading, and updating expenses, reports, invoices, and Gmail scans, but there are notable lifecycle gaps: no delete/void tools for expenses, income, reports, or invoices, and no update tool for income. Several descriptions explicitly redirect unsupported edits to the web app, confirming that the assistant cannot complete those workflows directly.

Resources