Skip to main content
Glama
samaxbytez

freeagent-mcp-server

by samaxbytez

freeagent_create_contact

Add a new contact to FreeAgent by supplying either a first/last name or an organization name, plus optional fields like email, phone, and address.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
first_nameNoContact first name
last_nameNoContact last name
organisation_nameNoOrganisation name
emailNoContact email address
phone_numberNoContact phone number
address1NoAddress line 1
address2NoAddress line 2
address3NoAddress line 3
townNoTown or city
postcodeNoPostal code
countryNoCountry
default_payment_terms_in_daysNoDefault payment terms in days
Behavior2/5

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

No annotations present, so description must fully disclose behavior. It only states the constraint but omits authentication requirements, error conditions, side effects, or any behavioral traits beyond creation.

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 sentences: first states purpose, second states constraint. No redundant information, well front-loaded.

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?

No output schema, yet description does not clarify return value, success indication, or error scenarios. With 12 parameters and complex constraints, the description is incomplete.

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% with descriptions for each parameter. The description adds value by specifying the mandatory combination of name fields, which is not enforced in the schema.

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?

Clearly states 'Create a new contact in FreeAgent' with a specific verb and resource, and distinguishes from other create tools by specifying the required fields.

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?

Explicitly states the requirement to provide either first_name+last_name or organisation_name, giving clear context for when to use. However, no mention of when not to use or alternatives like update_contact.

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/samaxbytez/freeagent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server