freeagent-mcp-server

List Timeslips

freeagent_list_timeslips

Read-only

Lists FreeAgent timeslips filtered by date range, user, task, project, or billing status, so you can review time entries and identify unbilled or running work.

Instructions

List timeslips from FreeAgent. Can be filtered by date range, user, task, project, and billing status.

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_list_timeslips"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number to fetch (default 1)
`task`	No	Filter by task URL
`user`	No	Filter by user URL
`view`	No	Filter by billing/running status
`project`	No	Filter by project URL
`to_date`	No	End date filter (YYYY-MM-DD)
`per_page`	No	Results per page (default 25, max 100). Check pagination.next_page in the response for more results.
`from_date`	No	Start date filter (YYYY-MM-DD)
`updated_since`	No	Only return timeslips updated since this timestamp

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.0.0Nov 6, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / page

Added value: +{
+  "description": "Page number to fetch (default 1)",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}

addedInput schema / properties / per_page

Added value: +{
+  "description": "Results per page (default 25, max 100). Check pagination.next_page in the response for more results.",
+  "maximum": 100,
+  "minimum": 1,
+  "type": "integer"
+}

First observedv1.3.0Jun 21, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds nothing beyond that — it says nothing about pagination, default result size, or what a returned timeslip looks like, leaving the per_page note in the schema to carry that load.

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 with the resource first and the filter surface second — nothing wasted. It is arguably too terse rather than bloated, but the structure is clean and front-loaded.

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 9-parameter read tool with no output schema and no annotations about returns, the description should at least signal the paginated list response and whether all filters are optional. It covers the filter surface but leaves the response shape and pagination model undocumented outside 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%, so the baseline is 3. The description restates five of the nine filters without adding format or semantics (URL vs ID, date format, timestamp semantics for updated_since), and omits page, per_page and updated_since entirely.

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 ('List timeslips from FreeAgent') and enumerates the filterable dimensions. It does not explicitly contrast itself with siblings like freeagent_get_timeslip, though the list/get naming already implies the split.

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 mention of date range, user, task, project and billing-status filters implies the retrieval scenarios, but there is no explicit when-to-use guidance, no exclusions, and no pointer to get_timeslip for single records or to the create/update/delete variants.

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

Deploy Server