Skip to main content
Glama

Create expense

create_expense

Log an expense for the business. Optionally link it to an activity, booking, or guide, and attach a receipt image.

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": {
      "amount_cents": "<amount_cents>",
      "spent_on": "<spent_on>"
    },
    "name": "create_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoAlias for image_base64.
vendorNo
categoryNoA short category, such as food, equipment, transport, lodging, permits, or other.
currencyNoA three-letter currency code. Defaults to the business currency.
filenameNoThe receipt file name. Used to infer content_type when it is omitted.
guide_idNo
spent_onYesThe date the money was spent, as YYYY-MM-DD.
booking_idNo
activity_idNo
business_idNoThe id of the business to act on, from list_businesses. Optional when this connection covers a single business.
descriptionNo
amount_centsYesThe amount in cents.
content_typeNoThe receipt image MIME type, such as image/jpeg. Required with image_base64 unless filename is set.
image_base64NoBase64-encoded receipt image (PNG, JPEG, WebP, GIF, or HEIC).
receipt_data_urlNoA data URL for the receipt image, if the image is not sent as base64.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive write in a closed system. The description adds useful context that expenses can be linked to an activity, booking, or guide and that a receipt image can be attached, but it does not explain permissions, duplicate handling, or whether linked resources must exist.

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?

Two short sentences front-load the action and then list optional capabilities. There is no redundant wording and every sentence adds useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter create tool with no output schema, the description covers the core purpose and optional links but leaves the main sibling ambiguity unresolved. It is sufficient only when combined with the schema and annotations, which do much of the work.

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?

The schema covers 67% of parameters, so the baseline is moderate. The description clarifies the three optional relationship IDs and receipt-image handling, but omits the required amount_cents/spent_on semantics, business scoping, currency, and category details.

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 states a specific verb and resource: 'Log an expense for the business.' It also flags optional linkage to an activity, booking, or guide and receipt attachment, making the core action clear. It does not explicitly differentiate from sibling add_expense_receipt, so not 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only usage cue is the purpose statement; there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as add_expense_receipt or update_expense. Optional linking is parameter detail, not usage guidance.

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.

Resources