Skip to main content
Glama
norman-finance

Norman Finance MCP Server

Official

create_recurring_invoice

Automatically generate invoices at customizable intervals for recurring billing needs. Specify frequency, start/end dates, and invoice counts to streamline regular payments for services or contracts.

Instructions

Create a recurring invoice that will automatically generate new invoices based on specified frequency.
Useful for contracts or services that bill on a regular basis.
Always ask for reccurring configuration, for example:
    - How often to generate invoices (weekly, monthly)
    - Number of units for frequency (e.g. 1 for monthly = every month, 2 = every 2 months)
    - Start date
    - End date
    - End invoice count (optional)
    
Ask for additional information if needed, for example:
    - If the client is not found, ask for the client details and create a new client if necessary.
    - If the invoice number is not provided, ask for it.
    - If the due date is not provided, ask for it.
    - If the payment terms are not provided, ask for it.
    - If the bank details are not provided, ask for it.

Args:
    client_id: ID of the client for the invoice
    items: List of invoice items, each containing name, quantity, rate, vatRate and total
    frequency_type: How often to generate invoices ("weekly", "monthly")
    frequency_unit: Number of units for frequency (e.g. 1 for monthly = every month, 2 = every 2 months)
    starts_from_date: Date to start generating invoices from (YYYY-MM-DD)
    ends_on_date: Optional end date for recurring invoices (YYYY-MM-DD). Either ends_on_date or ends_on_invoice_count should be provided.
    ends_on_invoice_count: Optional number of invoices to generate before stopping. Either ends_on_date or ends_on_invoice_count should be provided.
    invoice_number: Base invoice number (will be auto-generated if not provided)
    issued: Issue date in YYYY-MM-DD format
    due_to: Due date in YYYY-MM-DD format
    currency: Invoice currency (EUR, USD), by default it's EUR
    payment_terms: Payment terms text
    notes: Additional notes
    language: Invoice language (en, de)
    invoice_type: Type of invoice (SERVICES, GOODS)
    is_vat_included: Whether prices include VAT
    bank_name: Name of the bank
    iban: IBAN for payments
    bic: BIC/SWIFT code
    create_qr: Whether to create payment QR code
    color_schema: Invoice style color (hex code)
    font: Invoice font (e.g. "Plus Jakarta Sans", "Inter")
    is_to_send: Whether to send invoices automatically to client
    settings_on_overdue: Configuration for overdue notifications
    service_start_date: Service period start date (for SERVICES type)
    service_end_date: Service period end date (for SERVICES type)
    delivery_date: Delivery date (for GOODS type)

Returns:
    Information about the created recurring invoice setup and always include the generated invoice pdf url from reportUrl field

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bank_nameNo
bicNo
client_idYes
color_schemaNo#FFFFFF
create_qrNo
currencyNoEUR
delivery_dateNo
due_toNo
ends_on_dateNo
ends_on_invoice_countNo
fontNoPlus Jakarta Sans
frequency_typeYes
frequency_unitYes
ibanNo
invoice_numberNo
invoice_typeNoSERVICES
is_to_sendNo
is_vat_includedNo
issuedNo
itemsYes
languageNoen
notesNo
payment_termsNo
service_end_dateNo
service_start_dateNo
settings_on_overdueNo
starts_from_dateYes
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the creation of recurring invoices and mentions automatic generation, but lacks details about permissions, error handling, rate limits, or system behavior beyond the basic operation. The 'Always ask for...' and 'Ask for additional information...' sections provide some interaction guidance but not comprehensive behavioral traits.

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

Conciseness3/5

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

The description is appropriately front-loaded with the core purpose, but becomes verbose with detailed parameter guidance and a full parameter list that duplicates the schema. While the information is valuable, the structure could be more streamlined by separating high-level guidance from exhaustive parameter documentation.

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 complex creation tool with 27 parameters, no annotations, and no output schema, the description does a good job of explaining the tool's purpose, usage context, and parameter semantics. It includes return value information ('always include the generated invoice pdf url from reportUrl field'), though it could benefit from more behavioral context about the recurring invoice system's operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given 0% schema description coverage and 27 parameters, the description provides extensive parameter semantics beyond the schema. It explains the purpose of recurring configuration parameters (frequency_type, frequency_unit, starts_from_date, ends_on_date, ends_on_invoice_count), clarifies dependencies ('Either ends_on_date or ends_on_invoice_count should be provided'), and adds context for many other parameters through the 'Ask for additional information' section.

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 the tool's purpose: 'Create a recurring invoice that will automatically generate new invoices based on specified frequency.' It specifies the verb ('create'), resource ('recurring invoice'), and distinguishes it from sibling tools like 'create_invoice' by emphasizing the automated recurring nature.

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?

The description provides clear context for when to use this tool ('Useful for contracts or services that bill on a regular basis') and includes implicit guidance through examples of required information. However, it does not explicitly state when NOT to use it or name specific alternatives among siblings.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/norman-finance/norman-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server