Skip to main content
Glama

Create a fixed cost

recurring_create

Create a recurring fixed-cost template that automatically books expenses at set intervals, such as monthly rent, starting from the next due date.

Instructions

Create a new fixed-cost template (for example monthly rent) that the app books automatically as an expense every intervalMonths, starting at nextDueAt. Use it for charges that repeat; for a one-off payment use expense_create. It does not book a charge itself. Any member may create one. If paidByMemberId is not you, you must carry a positive share in splits, otherwise 403 paid_by_must_include_caller; members who left fail with 400 member_not_in_wg. Returns the new template as recurringExpense. The call carries an idempotency key, so a retried request is not created twice.

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": {
      "description": "<description>",
      "amountCents": "<amountCents>",
      "paidByMemberId": "<paidByMemberId>",
      "nextDueAt": "<nextDueAt>",
      "splits": "<splits>"
    },
    "name": "recurring_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
splitsYesWho owes what per charge, one entry per member. Amounts must add up to amountCents. Member ids come from members_list.
wgCodeNoShare code of the flat (code from wg_list). Leave it out when the account belongs to one flat.
categoryNoCategory given to each booked expense. Defaults to other.other
currencyNoFixed-cost templates are always in EUR, which is the only accepted value (the app rejects others with recurring_currency_unsupported). Omit it.EUR
nextDueAtYesWhen the first charge is due, ISO 8601 with offset. May lie up to 366 days in the past (then the app books the missed cycles) and up to 10 years ahead; later dates keep this day of the month.
amountCentsYesAmount of each charge in cents of EUR, for example 85000 for 850.00 EUR.
descriptionYesShort label shown in the expense list for every booked charge, for example "Rent".
intervalMonthsNoMonths between two charges: 1 monthly, 3 quarterly, 12 yearly. Defaults to 1.
paidByMemberIdYesMember who pays the charge and is owed the money back, from members_list. Usually the tenant who pays the landlord.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • addedInput schema / properties / currency / const
      Added value: +"EUR"
    • changedInput schema / properties / currency / description
      Previous value: -"Only EUR is accepted by the app; any other value fails with recurring_currency_unsupported. Omit it."New value: +"Fixed-cost templates are always in EUR, which is the only accepted value (the app rejects others with recurring_currency_unsupported). Omit it."
    • removedInput schema / properties / currency / enum
      Removed value: -[
      -  "EUR",
      -  "CHF",
      -  "USD",
      -  "GBP"
      -]
    • removedInput schema / properties / splits / items / description
      Removed value: -"One member share of each charge."
    • addedInput schema / properties / splits / items / properties / amountCents / description
      Added value: +"Share of this member in cents. All shares together must equal the total."
    • addedInput schema / properties / splits / items / properties / debtorMemberId / description
      Added value: +"Member who owes this share, from members_list. The payer may appear here to cover their own share."
  2. Changed9 schema fields changedv0.1.1
    • addedInput schema / properties / amountCents / description
      Added value: +"Amount of each charge in cents of EUR, for example 85000 for 850.00 EUR."
    • addedInput schema / properties / category / description
      Added value: +"Category given to each booked expense. Defaults to other."
    • addedInput schema / properties / currency / description
      Added value: +"Only EUR is accepted by the app; any other value fails with recurring_currency_unsupported. Omit it."
    • addedInput schema / properties / description / description
      Added value: +"Short label shown in the expense list for every booked charge, for example \"Rent\"."
    • addedInput schema / properties / intervalMonths / description
      Added value: +"Months between two charges: 1 monthly, 3 quarterly, 12 yearly. Defaults to 1."
    • addedInput schema / properties / nextDueAt / description
      Added value: +"When the first charge is due, ISO 8601 with offset. May lie up to 366 days in the past (then the app books the missed cycles) and up to 10 years ahead; later dates keep this day of the month."
    • addedInput schema / properties / paidByMemberId / description
      Added value: +"Member who pays the charge and is owed the money back, from members_list. Usually the tenant who pays the landlord."
    • addedInput schema / properties / splits / description
      Added value: +"Who owes what per charge, one entry per member. Amounts must add up to amountCents. Member ids come from members_list."
    • addedInput schema / properties / splits / items / description
      Added value: +"One member share of each charge."
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond the annotations: names the exact failure modes (403 paid_by_must_include_caller, 400 member_not_in_wg), states the authorization model (any member), and describes the return value ("the new template as recurringExpense"). The retry/idempotency-key sentence is useful, though it sits in mild tension with idempotentHint=false; the two are reconcilable (same key = safe retry, a new call creates a new template), but the description could have made that distinction explicit.

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?

Purpose and the sibling routing are front-loaded, and each sentence carries distinct information (scope, non-booking, permissions, error codes, return, idempotency). It is dense but nearly every clause earns its place; the error-code sentence is the only one that could be trimmed for a first-read.

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 9-parameter mutation with no output schema, the description covers what is created, when it triggers, who may call it, the cross-field constraint, the failure modes, and the returned object. Nothing an agent needs in order to call it correctly is missing.

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 real meaning: it ties intervalMonths and nextDueAt to the booking schedule, and adds a cross-field constraint not visible per-parameter in the schema (paidByMemberId outside the caller requires a positive share in splits). It does not explain splits aggregation or wgCode omission, which the schema already covers.

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?

"Create a new fixed-cost template ... that the app books automatically as an expense every intervalMonths" gives a specific verb, resource, and scheduling behavior, and immediately contrasts with the sibling "for a one-off payment use expense_create". An agent can distinguish recurring_create from expense_create without opening either schema.

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?

Explicit when-to-use ("charges that repeat") and when-not (one-off payments, routed to expense_create), plus the crucial clarification "It does not book a charge itself" so the agent does not expect an immediate expense. Prerequisites are also stated: any member may create, but if paidByMemberId is not the caller they must hold a positive share in splits.

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