Skip to main content
Glama

start_timer

Start tracking time for a specific timeslip in FreeAgent to record billable hours or project work duration.

Instructions

Start a timer for a timeslip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTimeslip ID

Implementation Reference

  • MCP CallToolRequest handler for the 'start_timer' tool. Extracts the timeslip ID from arguments and calls FreeAgentClient.startTimer(id), then returns the resulting timeslip as formatted JSON text content.
    case 'start_timer': {
      const { id } = request.params.arguments as { id: string };
      const timeslip = await this.client.startTimer(id);
      return {
        content: [{ type: 'text', text: JSON.stringify(timeslip, null, 2) }]
      };
    }
  • src/index.ts:161-171 (registration)
    Registration of the 'start_timer' tool in the ListToolsRequestSchema response, defining its name, description, and input schema (requiring a string 'id').
    {
      name: 'start_timer',
      description: 'Start a timer for a timeslip',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Timeslip ID' }
        },
        required: ['id']
      }
    },
  • Helper method in FreeAgentClient that implements the core logic: POST request to FreeAgent API `/timeslips/${id}/timer` to start the timer, returning the updated Timeslip object.
    async startTimer(id: string): Promise<Timeslip> {
        try {
            console.error('[API] Starting timer for timeslip:', id);
            const response = await this.axiosInstance.post<TimeslipResponse>(`/timeslips/${id}/timer`);
            return response.data.timeslip;
        } catch (error) {
            console.error('[API] Failed to start timer:', error);
            throw error;
        }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't explain what 'starting a timer' entails operationally—whether it's a write operation, if it requires specific permissions, what happens if a timer is already running, or what the expected outcome is. This leaves significant behavioral gaps for a mutation tool.

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 with zero wasted words. It's front-loaded with the core action and resource, making it immediately understandable. Every word earns its place without redundancy or unnecessary elaboration.

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 tool that performs a mutation (starting a timer) with no annotations and no output schema, the description is insufficient. It doesn't explain the behavioral implications, expected outcomes, or error conditions. Given the complexity of timer operations and the lack of structured data, more context is needed to make this tool usable for an AI agent.

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 the single parameter 'id' documented as 'Timeslip ID' in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as format examples or constraints. The baseline score of 3 is appropriate given the schema handles the parameter documentation adequately.

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 action ('Start a timer') and the target resource ('for a timeslip'), providing a specific verb+resource combination. However, it doesn't differentiate from sibling tools like 'stop_timer' or explain what distinguishes starting a timer from creating/updating a timeslip.

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 'create_timeslip' or 'update_timeslip'. It doesn't mention prerequisites (e.g., needing an existing timeslip ID) or clarify the relationship with 'stop_timer'. There's minimal implied usage context beyond the basic action.

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