freeagent-mcp-server

Create Timeslip

freeagent_create_timeslip

Create a FreeAgent timeslip to track time against a project task by specifying user, project, task, date, and hours.

Instructions

Create a new timeslip in FreeAgent for tracking time against a project task.

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": {
      "user": "<user>",
      "project": "<project>",
      "task": "<task>",
      "dated_on": "<dated_on>",
      "hours": "<hours>"
    },
    "name": "freeagent_create_timeslip"
  }
}

Input Schema

Name	Required	Description
`task`	Yes	Task URL
`user`	Yes	User URL
`hours`	Yes	Number of hours as a decimal string
`comment`	No	Optional comment for the timeslip
`project`	Yes	Project URL
`dated_on`	Yes	Date for the timeslip (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.0.0Nov 6, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
First observedv1.3.0Jun 21, 2026

TDQS

B3.2/5.0

Behavior3/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 covered structurally. The description adds the useful scoping fact that time is tracked against a project task, but says nothing about whether the record is immediately billable, what happens on duplicate 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.

Conciseness4/5

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

A single front-loaded sentence with no filler. It is efficient, though it could have spent the same space on routing guidance instead of restating the domain name.

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?

For a six-parameter mutation with no output schema, the definition is adequate but thin: it does not say what the response contains (presumably the created timeslip), nor that the required fields are URL references rather than names. Annotations carry the safety profile, so the remaining gap is moderate rather than severe.

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 parameter including the optional comment is documented inline, which sets the baseline at 3. The phrase "tracking time against a project task" mildly hints that project and task are linked, but adds no format or constraint detail beyond the schema.

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 timeslip") plus the domain (FreeAgent) and intent (tracking time against a project task). It does not distinguish itself from siblings such as freeagent_start_timer or freeagent_update_timeslip, so the agent must infer which creation path to use.

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?

The description gives no when-to-use guidance, no exclusions, and no mention of alternatives like freeagent_start_timer for live tracking or freeagent_list_timeslips for reads. Nothing tells the agent which prerequisites (existing user, project, task URLs) must be resolved before calling.

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

Deploy Server