Skip to main content
Glama
OxygenBubbles

FreeAgent MCP Server

freeagent_explain_transaction

Idempotent

Approve and update FreeAgent bank transaction explanations: change category, add description, attach receipts, and mark transactions as explained.

Instructions

Approve or update a FreeAgent bank transaction explanation. Use this to:

  • Approve a 'marked for review' transaction (set markExplained=true)

  • Change the category or description of an explanation

  • Attach a receipt/invoice — PREFER filePath (a local file) or fileUrl (a download link); the server reads/encodes it. Re-attaching replaces any existing attachment. Get the explanationId from freeagent_list_transactions (explanation_id field).

RECEIPTS: Before asking the user for a file, search connected email tools (Gmail, Outlook/M365) for a matching invoice using vendor name, amount and date. Pass a download link as fileUrl, or save the PDF locally and pass filePath. Avoid fileBase64 for anything but tiny files — large inline base64 is unreliable. Also check local file sources (Downloads folder, etc.) if the user has mentioned them.

SAFETY: Only set markExplained=true when you have a confirmed receipt attached or the user has explicitly approved it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
explanationIdYesNumeric FreeAgent bank transaction explanation ID (from explanation_id in list_transactions)
descriptionNoHuman-readable description for the transaction (e.g. 'IONOS — Monthly cloud hosting')
categoryNoFreeAgent category path (e.g. '/v2/categories/285'). Use freeagent_list_categories to find the right one.
markExplainedNoSet true to approve/reconcile the transaction. Only do this when evidence is attached or confirmed.
fileBase64NoBase64-encoded file to attach (receipt, invoice, screenshot — PDF, PNG, JPEG, etc.)
fileNameNoFile name for the attachment (e.g. 'ionos-invoice-apr-2026.pdf')
contentTypeNoMIME type of the file (e.g. 'application/pdf', 'image/jpeg', 'image/png'). Inferred from fileName/filePath if omitted.
filePathNoAbsolute path to a local file to attach (e.g. '/Users/you/Downloads/invoice.pdf'). The SERVER reads and base64-encodes it — PREFER THIS over fileBase64, which is unreliable for non-trivial files. fileName defaults to the file's name.
fileUrlNoURL of a receipt to download and attach (e.g. a Stripe 'Download invoice' link). The server fetches and encodes it — no need to handle bytes.
Behavior5/5

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

Discloses behavioral traits beyond annotations: it's a mutation that can approve or update, explains that re-attaching a file replaces any existing attachment, and includes safety warnings about markExplained. The annotations show idempotentHint=true and destructiveHint=false, and the description aligns with these traits.

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 sections (main purpose, RECEIPTS, SAFETY) and is front-loaded with the primary action. While somewhat lengthy, every sentence adds value. Could be slightly more concise, but the detail is warranted given the tool's complexity.

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?

Given 9 parameters, 100% schema coverage, and no output schema, the description is comprehensive. It covers attachment methods, safety guidelines, where to get the explanationId, and references related tools (Gmail, Outlook, local file sources). No gaps remain for effective use.

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?

Adds significant meaning to parameters beyond the input schema. For example, it explains the preference order for file attachment methods (filePath/fileUrl over fileBase64), clarifies that filePath is read and encoded by the server, and notes that explanationId comes from freeagent_list_transactions. Schema coverage is 100%, but the description enriches each parameter.

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 it approves or updates a FreeAgent bank transaction explanation, with specific actions like attaching receipts and changing category/description. It references the sibling tool freeagent_list_transactions for the explanationId, but does not explicitly differentiate from other sibling tools like freeagent_create_expense.

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?

Provides explicit guidance: when to set markExplained (only with confirmed receipt or user approval), how to attach files (prefer filePath/fileUrl over fileBase64), and instructs to search email tools for matching invoices before asking the user. This helps the agent make correct decisions.

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