Skip to main content
Glama
Sign In
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

freeagent_create_credit_note

Create a new credit note in FreeAgent for a contact with a specified date, including optional line items, comments, currency, and payment terms.

Instructions

Create a new credit note 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>"
    },
    "name": "freeagent_create_credit_note"
  }
}

Input Schema

NameRequiredDescriptionDefault
contactYesContact URL for the credit note
commentsNoComments or notes for the credit note
currencyNoCurrency code, e.g. GBP, USD
dated_onYesCredit note date in YYYY-MM-DD format
credit_note_itemsNoJSON array of credit note line items, each with item_type, quantity, price, description
payment_terms_in_daysNoPayment terms in days

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.5/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 write/non-destructive profile is covered. Beyond that the description adds nothing: it does not say whether creating is idempotent, whether the note starts in draft, what happens to any accounting entries, or what is returned.

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?

It is a single short sentence with zero wasted words, which is structurally clean. But the economy comes from omission rather than precision, so the brevity is not earning much value.

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?

This is a mutation tool with six parameters, two required, and no output schema, so the description should carry real weight. A one-line restatement leaves out required-field expectations, the JSON format of credit_note_items, currency defaults, and the effect on the business's books.

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%, so every one of the six parameters is already documented in the schema, including the required contact URL and YYYY-MM-DD date format. The description adds no extra meaning, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a verb ('Create') and resource ('credit note'), which does distinguish it from get/list/update/delete credit note siblings. However, it is essentially a restatement of the tool name with 'in FreeAgent' appended and adds no scope details such as what a credit note requires or how it relates to invoices.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. an existing contact URL is required), and no pointer to alternatives such as freeagent_create_invoice or freeagent_update_credit_note. The agent must infer the entire usage context from the name and schema.

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