Skip to main content
Glama
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez

freeagent_create_invoice

Create a new FreeAgent invoice from a contact, invoice date, payment terms, and optional line items to record billable work or products.

Instructions

Create a new invoice in FreeAgent

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contact": "<contact>",
      "dated_on": "<dated_on>",
      "payment_terms_in_days": "<payment_terms_in_days>"
    },
    "name": "freeagent_create_invoice"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYesContact URL (e.g. https://api.freeagent.com/v2/contacts/123)
commentsNoComments to appear on the invoice
currencyNoCurrency code (e.g. GBP, USD)
dated_onYesInvoice date (YYYY-MM-DD)
ec_statusNoEC status for EU VAT
referenceNoInvoice reference
exchange_rateNoExchange rate
invoice_itemsNoJSON string of array of invoice items. Each item has fields: item_type (Hours/Days/Weeks/Months/Years/Products/Comment/Rebilling), quantity (string), price (string), description (string)
payment_methodsNoPayment methods
payment_terms_in_daysYesPayment terms in days (e.g. 30)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.0.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is known, but the description adds nothing beyond it. For a mutation tool it should disclose the resulting invoice state (draft?), whether the invoice is emailed, and what happens when invoice_items is omitted. None of that context is present.

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?

A single front-loaded sentence with no filler, but it is undersized for a 10-parameter creation tool with a nested JSON-string argument. Brevity here is under-specification rather than effective conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 10 parameters (3 required), a mutation with no output schema, and a tricky-string item array, the one-line description leaves the agent without side-effect, state, or return information. Annotations cover mutability only, so the description should do much more.

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

Parameters3/5

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

Schema description coverage is 100%, including the non-obvious invoice_items JSON string format, so the schema carries the parameter semantics and the baseline 3 applies. The description contributes zero parameter meaning on top of that.

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?

States a specific verb and resource ("Create a new invoice"), which is unambiguous and clearly distinct from the update/delete/list/mark_* invoice siblings by name. It stops short of any explicit differentiation sentence or scope note, so it sits at clear-but-undifferentiated.

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?

No guidance on when to use this versus freeagent_create_estimate (or converting an estimate), freeagent_create_credit_note, or freeagent_update_invoice. Nothing about prerequisites such as needing an existing contact URL or having items ready, and no mention of what happens after creation (draft vs sent status).

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

Deploy Server

Other Tools