FreeAgent MCP Server

freeagent_create_bill

Record supplier invoices received by the company, specifying spending categories and tax-inclusive line values. Searches connected email for the original invoice PDF and attaches it to the bill.

Instructions

Record a supplier bill (an invoice the company has received and owes). Each line needs a spending category and a value including tax.

RECEIPTS: before asking the user for the PDF, search connected email tools (Gmail, Outlook/M365) for the supplier invoice and pass it as fileBase64 + fileName.

Input Schema

TableJSON Schema

Name	Required	Description
`dueOn`	Yes	Payment due date YYYY-MM-DD
`items`	Yes	Bill line items — at least one, at most 40
`contact`	Yes	Supplier the bill is from — create one with freeagent_create_contact
`datedOn`	Yes	Bill date YYYY-MM-DD
`project`	No	Project to allocate this bill to
`currency`	No	ISO 4217 currency (default: company currency)
`fileName`	No	File name (e.g. 'invoice.pdf')
`reference`	Yes	Supplier's invoice reference (e.g. 'INV-2049')
`fileBase64`	No	Base64-encoded supplier invoice (PDF, PNG, JPEG)
`rebillType`	No	How to rebill this to the client
`contentType`	No	MIME type. Inferred from fileName if omitted.
`rebillFactor`	No	Markup percentage or fixed price — required for markup/price

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv3.0.1Aug 21, 2026

addedInput schema / $schema

Added value: +"http://json-schema.org/draft-07/schema#"

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / contact

Added value: +{
+  "description": "Supplier the bill is from — create one with freeagent_create_contact",
+  "pattern": "^(?:https:\\/\\/api\\.freeagent\\.com)?\\/v2\\/contacts\\/\\d+$",
+  "type": "string"
+}

addedInput schema / properties / contentType

Added value: +{
+  "description": "MIME type. Inferred from fileName if omitted.",
+  "type": "string"
+}

addedInput schema / properties / currency

Added value: +{
+  "description": "ISO 4217 currency (default: company currency)",
+  "pattern": "^[A-Z]{3}$",
+  "type": "string"
+}

addedInput schema / properties / datedOn

Added value: +{
+  "description": "Bill date YYYY-MM-DD",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / dueOn

Added value: +{
+  "description": "Payment due date YYYY-MM-DD",
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

addedInput schema / properties / fileBase64

Added value: +{
+  "description": "Base64-encoded supplier invoice (PDF, PNG, JPEG)",
+  "maxLength": 6990000,
+  "type": "string"
+}

addedInput schema / properties / fileName

Added value: +{
+  "description": "File name (e.g. 'invoice.pdf')",
+  "type": "string"
+}

addedInput schema / properties / items

Added value: +{
+  "description": "Bill line items — at least one, at most 40",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "categoryUrl": {
+        "description": "Spending category for this line",
+        "pattern": "^(?:https:\\/\\/api\\.freeagent\\.com)?\\/v2\\/categories\\/\\d+$",
+        "type": "string"
+      },
+      "description": {
+        "description": "Line description",
+        "maxLength": 500,
+        "type": "string"
+      },
+      "salesTaxRate": {
+        "description": "VAT rate (e.g. '20.0')",
+        "pattern": "^\\d+(\\.\\d+)?$",
+        "type": "string"
+      },
+      "totalValue": {
+        "description": "Line value INCLUDING tax (e.g. '120.00'). Must be positive — a supplier credit is a credit note, not a negative bill line.",
+        "pattern": "^\\d+(\\.\\d{1,2})?$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "categoryUrl",
+      "totalValue"
+    ],
+    "type": "object"
+  },
+  "maxItems": 40,
+  "minItems": 1,
+  "type": "array"
+}

addedInput schema / properties / project

Added value: +{
+  "description": "Project to allocate this bill to",
+  "pattern": "^(?:https:\\/\\/api\\.freeagent\\.com)?\\/v2\\/projects\\/\\d+$",
+  "type": "string"
+}

addedInput schema / properties / rebillFactor

Added value: +{
+  "description": "Markup percentage or fixed price — required for markup/price",
+  "pattern": "^\\d+(\\.\\d+)?$",
+  "type": "string"
+}

addedInput schema / properties / rebillType

Added value: +{
+  "description": "How to rebill this to the client",
+  "enum": [
+    "cost",
+    "markup",
+    "price"
+  ],
+  "type": "string"
+}

addedInput schema / properties / reference

Added value: +{
+  "description": "Supplier's invoice reference (e.g. 'INV-2049')",
+  "maxLength": 100,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / required

Added value: +[
+  "contact",
+  "reference",
+  "datedOn",
+  "dueOn",
+  "items"
+]

Addedv3.0.0Aug 7, 2026

TDQS

A4.2/5.0

Behavior3/5

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

The description says 'Record', which appropriately signals a state-changing operation and matches the annotations. However, it does not disclose side effects beyond creation, such as whether duplicate calls create duplicate bills, or whether special permissions are required. Annotations cover read-only/destructive/idempotent hints, but the description adds little independent behavioral context.

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 short, front-loaded with the core purpose, and every sentence contributes either to tool selection or to an efficient workflow. The RECEIPTS note is prominent without being verbose.

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 table with 12 parameters, the description plus fully covered schema is enough for an agent to construct a valid call. It does not explain return values, but there is no output schema and create-tool output is not usually self-serve. A small gap is not explicitly stating what to do if no email match is found, though it is reasonably implied.

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. The description adds value by emphasizing that every line requires a category and a value including tax, and it explains how fileBase64 and fileName should be supplied when a matching invoice is found in email tools. This is actionable semantics beyond the raw schema descriptions.

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 opens with a specific action and resource: 'Record a supplier bill', with the parenthetical 'an invoice the company has received and owes' removing ambiguity. This clearly separates the tool from invoice creation for customers and from expense recording without needing to inspect the schema.

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?

It gives clear context for when to use the tool: recording supplier bills. The RECEIPTS section adds a concrete workflow instruction by telling the agent to search Gmail/Outlook for the supplier invoice before asking the user for a PDF. It does not explicitly name alternative tools or exclusion cases, but the contextual cue is strong enough to guide selection.

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

freeagent_create_bill

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools