Skip to main content
Glama
norman-finance

Norman Finance MCP Server

Official

create_transaction

Create manual transactions in Norman Finance MCP Server by specifying amount, description, cashflow type, and supplier country. Automatically categorize transactions or assign VAT rates, sale types, and dates for accurate financial records.

Instructions

Create a new manual transaction.

Args:
    amount: Transaction amount (positive for income, negative for expense)
    description: Transaction description
    category: Transaction category
    date: Transaction date in YYYY-MM-DD format (defaults to today)
    vat_rate: VAT rate (0, 7, 19)
    sale_type: Sale type (GOODS, SERVICES)
    supplier_country: Country of the supplier (DE, INSIDE_EU, OUTSIDE_EU)
    cashflow_type: Cashflow type of the transaction (INCOME, EXPENSE)
    category_id: Category ID of the transaction (If not provided, the transaction will be categorized automatically using AI)
Returns:
    Information about the created transaction

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYes
cashflow_typeYes
category_idNo
dateNo
descriptionYes
sale_typeNo
supplier_countryYes
vat_rateNo
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this creates a transaction but doesn't mention permissions required, whether it's idempotent, error conditions, or what 'manual' implies operationally. The return statement is vague ('Information about the created transaction') without detailing format or structure.

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?

The description is well-structured with clear sections (Args, Returns) and uses bullet-like formatting. Every sentence adds value, though the opening line is somewhat redundant with the tool name. It could be slightly more front-loaded with key behavioral 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 creation tool with 8 parameters, no annotations, and no output schema, the description does well on parameters but lacks behavioral context. It explains what each parameter does but not how the tool behaves overall, what errors might occur, or what the return data contains. This leaves significant gaps for the agent to operate effectively.

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?

The description provides excellent parameter semantics beyond the 0% schema coverage. It explains each parameter's purpose, format constraints (e.g., 'YYYY-MM-DD format'), default behaviors ('defaults to today'), value meanings (e.g., 'positive for income, negative for expense'), and special logic ('categorized automatically using AI' for category_id). This fully compensates for the schema's lack of descriptions.

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 clearly states the verb ('Create') and resource ('manual transaction'), making the purpose unambiguous. It distinguishes from siblings like 'update_transaction' or 'search_transactions' by focusing on creation. However, it doesn't explicitly differentiate from 'create_invoice' or 'create_recurring_invoice', which might be related transaction types.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, when manual transactions are appropriate versus automated ones, or how this differs from similar tools like 'create_invoice'. The agent must infer usage from context alone.

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