freeagent-mcp-server

Start Timer

freeagent_start_timer

Starts a running timer on a FreeAgent timeslip using its ID, so elapsed time accumulates until the timer is stopped.

Instructions

Start a running timer on a timeslip. The timeslip will accumulate time until the timer is stopped.

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": {
      "timeslip_id": "<timeslip_id>"
    },
    "name": "freeagent_start_timer"
  }
}

Input Schema

Name	Required	Description	Default
`timeslip_id`	Yes	The timeslip ID

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

A3.5/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 mutation and closed-world nature are covered. The description adds real value by disclosing the stateful accumulation behavior ('will accumulate time until the timer is stopped'), but it does not say what happens if a timer is already running, whether starting is idempotent, or what side effects occur on the timeslip's duration fields.

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?

Two short sentences, front-loaded with the action; the second sentence earns its place by explaining the accumulating behavior. No filler or redundancy.

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

Completeness4/5

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

For a one-parameter mutation tool with annotations and no output schema, the definition covers what the call does and the ongoing behavior it triggers. It leaves minor gaps around the response payload and error conditions when a timer is already active, but nothing critical for correct invocation.

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% for the single timeslip_id parameter, so the baseline is 3. The description confirms the timer accrues against that specific timeslip but adds no format, sourcing, or lookup guidance 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: 'Start a running timer on a timeslip.' An agent immediately knows the action and target. It does not name the sibling freeagent_stop_timer explicitly, so sibling differentiation is only implied by 'until the timer is stopped.'

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?

The required timeslip_id is implied as the target, and the second sentence hints that stopping is a separate action (freeagent_stop_timer), but the description never states when to start a timer versus logging time via freeagent_update_timeslip, nor any prerequisites such as the timeslip needing to be in a non-billed state.

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

Deploy Server