Skip to main content
Glama
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez

freeagent_create_contact

Add a new individual or organisation contact to FreeAgent by supplying a first and last name or an organisation name, plus optional email, phone, address, and payment terms.

Instructions

Create a new contact in FreeAgent. Must provide either first_name and last_name, or organisation_name.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "freeagent_create_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
townNoTown or city
emailNoContact email address
countryNoCountry
address1NoAddress line 1
address2NoAddress line 2
address3NoAddress line 3
postcodeNoPostal code
last_nameNoContact last name
first_nameNoContact first name
phone_numberNoContact phone number
organisation_nameNoOrganisation name
default_payment_terms_in_daysNoDefault payment 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

A3.6/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world write, so the safety profile is covered. The description adds the cross-field identity requirement but says nothing about permissions, duplicate detection, side effects, or whether the created record 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero filler, with the operation stated first and the binding constraint immediately after. Nothing is wasted or buried.

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

Completeness3/5

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

With 12 optional parameters, no output schema, and no required fields, the description covers the single most important calling constraint. It is not sufficient on its own for an agent to predict success conditions (duplicate emails, org-vs-individual field combinations) or the response payload.

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 per-parameter meaning is already handled by the schema and the baseline would be 3. The description earns above baseline by surfacing a cross-field constraint the schema cannot express (zero required fields, yet one of two field combinations must be supplied).

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 states a specific verb and resource ("Create a new contact in FreeAgent"), which cleanly separates it from the list/get/update/delete contact siblings. It stops short of explicitly naming or contrasting those siblings, but the create operation is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one concrete invocation rule — supply either first_name+last_name or organisation_name — which is genuinely useful pre-call guidance. However, there is no statement of when to prefer creating a contact versus updating an existing one, no prerequisite/auth notes, and no guidance on duplicate handling.

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