Skip to main content
Glama

list_timeslips

Retrieve timeslip records from FreeAgent with filters for date ranges, status, users, tasks, or projects to track billable hours and time entries.

Instructions

List timeslips with optional filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
from_dateNoStart date (YYYY-MM-DD)
to_dateNoEnd date (YYYY-MM-DD)
updated_sinceNoISO datetime
viewNoFilter view type
userNoFilter by user URL
taskNoFilter by task URL
projectNoFilter by project URL
nestedNoInclude nested resources

Implementation Reference

  • MCP tool handler for 'list_timeslips': delegates to FreeAgentClient.listTimeslips and formats response as JSON.
    case 'list_timeslips': {
      const timeslips = await this.client.listTimeslips(request.params.arguments);
      return {
        content: [{ type: 'text', text: JSON.stringify(timeslips, null, 2) }]
      };
    }
  • Input schema defining optional parameters for filtering timeslips.
    inputSchema: {
      type: 'object',
      properties: {
        from_date: { type: 'string', description: 'Start date (YYYY-MM-DD)' },
        to_date: { type: 'string', description: 'End date (YYYY-MM-DD)' },
        updated_since: { type: 'string', description: 'ISO datetime' },
        view: {
          type: 'string',
          enum: ['all', 'unbilled', 'running'],
          description: 'Filter view type'
        },
        user: { type: 'string', description: 'Filter by user URL' },
        task: { type: 'string', description: 'Filter by task URL' },
        project: { type: 'string', description: 'Filter by project URL' },
        nested: { type: 'boolean', description: 'Include nested resources' }
      }
  • src/index.ts:85-104 (registration)
    Tool registration in the MCP ListTools response, including name, description, and input schema.
    {
      name: 'list_timeslips',
      description: 'List timeslips with optional filtering',
      inputSchema: {
        type: 'object',
        properties: {
          from_date: { type: 'string', description: 'Start date (YYYY-MM-DD)' },
          to_date: { type: 'string', description: 'End date (YYYY-MM-DD)' },
          updated_since: { type: 'string', description: 'ISO datetime' },
          view: {
            type: 'string',
            enum: ['all', 'unbilled', 'running'],
            description: 'Filter view type'
          },
          user: { type: 'string', description: 'Filter by user URL' },
          task: { type: 'string', description: 'Filter by task URL' },
          project: { type: 'string', description: 'Filter by project URL' },
          nested: { type: 'boolean', description: 'Include nested resources' }
        }
      }
  • Core implementation: FreeAgentClient method that performs the API GET request to retrieve timeslips with optional filters.
    async listTimeslips(params?: {
        from_date?: string;
        to_date?: string;
        updated_since?: string;
        view?: 'all' | 'unbilled' | 'running';
        user?: string;
        task?: string;
        project?: string;
        nested?: boolean;
    }): Promise<Timeslip[]> {
        try {
            console.error('[API] Fetching timeslips with params:', params);
            const response = await this.axiosInstance.get<TimeslipsResponse>('/timeslips', { params });
            return response.data.timeslips;
        } catch (error) {
            console.error('[API] Failed to fetch timeslips:', error);
            throw error;
        }
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'List timeslips' which implies a read-only operation, but doesn't cover critical aspects like pagination, rate limits, authentication requirements, or what 'list' entails (e.g., returns all timeslips or a subset). This is a significant gap for a tool with 8 parameters and no output schema.

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?

The description is a single, efficient sentence that front-loads the core action ('List timeslips') and adds a concise qualifier ('with optional filtering'). There is no wasted text, making it appropriately sized and well-structured.

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?

Given the complexity (8 parameters, no output schema, and no annotations), the description is insufficient. It doesn't explain return values, behavioral traits like pagination or ordering, or how filtering interacts with parameters. For a list operation with multiple filters, more context is needed to guide effective use.

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 input schema fully documents all 8 parameters with descriptions and an enum for 'view'. The description adds minimal value by mentioning 'optional filtering', which loosely relates to parameters like 'from_date' and 'view', but doesn't provide additional semantics beyond what the schema already covers.

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 clearly states the verb ('List') and resource ('timeslips') with the additional context of 'optional filtering', which makes the purpose understandable. However, it doesn't explicitly differentiate this tool from its sibling 'get_timeslip' (singular retrieval) or other list-like operations, missing full sibling distinction.

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 provides no guidance on when to use this tool versus alternatives like 'get_timeslip' for single timeslip retrieval or 'create_timeslip' for creation. It mentions 'optional filtering' but doesn't specify scenarios or exclusions, leaving usage context implied at best.

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

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