Skip to main content
Glama
freeagent-mcp-server

freeagent-mcp-server

by samaxbytez

freeagent_create_project

Create a new FreeAgent project with contact, budget, status, and currency details to set up project tracking and billing.

Instructions

Create a new project 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>",
      "name": "<name>",
      "status": "<status>",
      "budget": "<budget>",
      "budget_units": "<budget_units>",
      "currency": "<currency>"
    },
    "name": "freeagent_create_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesProject name
budgetYesProject budget
statusYesProject status
contactYesContact URL
ends_onNoProject end date (YYYY-MM-DD)
is_ir35NoWhether the project is IR35
currencyYesCurrency code
starts_onNoProject start date (YYYY-MM-DD)
budget_unitsYesBudget units
hours_per_dayNoHours per day
billing_periodNoBilling period
normal_billing_rateNoNormal billing rate
uses_project_invoice_sequenceNoWhether to use project invoice sequence

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.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the write/safe profile is covered. The description adds nothing further: no mention of side effects, whether a project becomes immediately visible or active, permission requirements, or how the required contact reference is resolved.

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?

A single front-loaded sentence with zero filler. It is efficient, though the brevity tips into under-specification rather than disciplined concision.

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?

For a 13-parameter creation tool with 6 required fields and no output schema, the description is thin. It does not explain the required contact URL, the budget/currency coupling, or what a successful call returns, leaving the agent to reconstruct all of that from the schema.

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% with 13 documented parameters, so the schema carries the parameter burden and the baseline of 3 applies. The description contributes no additional meaning about required fields such as budget, budget_units, or currency.

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 gives a specific verb+resource ('Create a new project') and names the product context (FreeAgent), which cleanly separates it from freeagent_update_project, freeagent_delete_project, and freeagent_list_projects. It does not explicitly call out those siblings, but the create semantics are unambiguous.

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 guidance on when to use this versus the update or get variants, no prerequisites, and no note that a contact must already exist before a project can be created. The agent must infer all usage conditions from the schema alone.

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