Skip to main content
Glama

Create recurring expense

crunch_create_recurring_expense

Creates a recurring expense template with supplier details, line items, and a schedule so Crunch automatically generates future expenses on the specified dates.

Instructions

Set up a recurring expense: a template expense (supplier, lines, optional payment method) that Crunch creates automatically on a schedule. Schedule values are Crunch's own; look at an existing one with crunch_get_recurring_expense if you're unsure of the names.

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": {
      "line_items": "<line_items>",
      "recurrence": "<recurrence>"
    },
    "name": "crunch_create_recurring_expense"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoInternal note
extraNoAdditional raw ExpenseDto fields, using Crunch's own field names (advanced). Merged last.
dry_runNoPreview: return the request that would be sent (for an update, the fields that would change) without sending it
line_itemsYesOne or more lines, each with its own expense type, VAT type and amount
recurrenceYesThe schedule
supplier_idNoSupplier ID (see crunch_list_suppliers). Give this or supplier_name.
posting_dateNoDate on the template expense (defaults to the first occurrence)
supplier_nameNoInstead of supplier_id: the supplier's exact name
payment_methodNoPayment method for the created expenses, for example EFT
bank_account_idNoBank account the payments come from
create_supplierNoWith supplier_name: create the supplier if it doesn't exist yet (default false)
supplier_referenceNoThe supplier's invoice or receipt number

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false). The description adds genuinely new behavioral context — that this creates a template which Crunch then materialises repeatedly on a schedule, which is the key consequence an agent must understand before calling. It stops short of saying how to stop or alter the schedule afterwards.

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 sentences, front-loaded with the core action and the template concept, then the discovery hint. No filler and nothing repeated from the schema or annotations.

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 12-parameter tool with nested objects and no output schema, the description covers purpose, the recurring side effect, and where to find valid recurrence names. It omits what the call returns (created template ID, first occurrence) and any permission or supplier-resolution caveats, which are minor but real gaps.

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?

Schema description coverage is 100% and the nested line_items/recurrence objects are documented in detail, so the schema carries the parameter burden. The description's only added semantic content is the warning that recurrence values use Crunch's own naming and should be copied from an existing record — useful, but already echoed in the schema field text.

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?

States a specific verb and resource ('Set up a recurring expense') and then defines the concept operationally: a template expense (supplier, lines, optional payment method) that Crunch creates automatically on a schedule. That distinguishes it in substance from crunch_create_expense, though the description never names the one-off sibling explicitly.

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?

Gives a concrete escape hatch for the trickiest part of the call: 'Schedule values are Crunch's own; look at an existing one with crunch_get_recurring_expense if you're unsure of the names.' It does not state when to choose this over crunch_create_expense or crunch_update_recurring_expense, so the guidance is clear but not exhaustive.

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

Deploy Server

Other Tools