Skip to main content
Glama
OxygenBubbles

FreeAgent MCP Server

freeagent_create_expense

Create expenses for personal card or cash purchases needing reimbursement. Supply vendor, date, amount, and description; optionally include a receipt or link to a bank transaction.

Instructions

Create an expense in FreeAgent — for purchases on a personal card or cash that need claiming back. Provide vendor, date, amount, description and category. If categoryUrl is omitted, auto-selects from vendor mapping. Optionally pass bankAccountId to auto-match and explain a corresponding bank transaction (e.g. if the same purchase also appears on a company card).

RECEIPTS: Before asking the user for a file, search connected email tools (Gmail, Outlook/M365) for a matching invoice. Use vendor name, amount and date as search terms. Download the PDF and pass it as fileBase64 + fileName. Also check local sources (Downloads folder, etc.) if the user has mentioned them.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vendorYesVendor / merchant name (e.g. 'IONOS Cloud')
datedOnYesExpense date YYYY-MM-DD
grossAmountYesGross amount as string (e.g. '22.80')
descriptionYesExpense description (e.g. 'Monthly cloud hosting')
currencyNoISO 4217 currency code (default GBP)GBP
vatAmountNoVAT amount as string (e.g. '3.80')
categoryUrlNoFreeAgent category URL (e.g. '/v2/categories/285'). Auto-selected from vendor if omitted.
fileBase64NoBase64-encoded receipt file (PDF, PNG, JPEG, etc.)
fileNameNoFile name for the receipt (e.g. 'receipt.pdf')
contentTypeNoMIME type (e.g. 'application/pdf'). Inferred from fileName if omitted.
bankAccountIdNoIf supplied, search this bank account for a matching unexplained transaction (same amount, date ±4 days) and link the expense to it.
Behavior4/5

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

The description discloses key behaviors: auto-selection of category from vendor mapping, optional bank transaction matching with date range, and receipt attachment process. Annotations only provide readOnlyHint=false and destructiveHint=false, so the description adds significant behavioral context beyond structured fields.

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?

The description is concise (two short paragraphs) and well-structured, with the first paragraph covering core parameters and the second providing receipt handling instructions. Every sentence adds necessary information.

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?

With 11 parameters and no output schema, the description covers the main workflow, parameter semantics, and additional receipt guidance. It lacks explicit mention of return values, but otherwise feels complete for an expense creation tool.

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% with descriptions, but the tool description adds value by explaining that 'categoryUrl' is auto-selected from vendor if omitted and that 'bankAccountId' triggers a search and link process. This goes beyond the schema's scope.

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 'Create an expense in FreeAgent' with a specific use case: purchases on personal card or cash that need claiming back. It distinguishes from sibling tools like 'freeagent_create_mileage_expense' by focusing on non-mileage expenses.

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 specifies when to use (personal card/cash expenses) and provides guidance on optional bank account matching and receipt handling. It contradicts its intended context, but doesn't explicitly say when not to use, though the sibling list provides implicit differentiation.

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

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/OxygenBubbles/freeagent-mcp-server'

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