Skip to main content
Glama

stop_timer

Stop tracking time on a specific timeslip to record work duration in FreeAgent.

Instructions

Stop a running timer for a timeslip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTimeslip ID

Implementation Reference

  • MCP tool handler for 'stop_timer': extracts timeslip ID from arguments and calls client.stopTimer(id), returning the updated timeslip as JSON.
    case 'stop_timer': {
      const { id } = request.params.arguments as { id: string };
      const timeslip = await this.client.stopTimer(id);
      return {
        content: [{ type: 'text', text: JSON.stringify(timeslip, null, 2) }]
      };
    }
  • src/index.ts:172-182 (registration)
    Registers the 'stop_timer' tool in the MCP server's list_tools response, including name, description, and input schema requiring a timeslip ID.
    {
      name: 'stop_timer',
      description: 'Stop a running timer for a timeslip',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Timeslip ID' }
        },
        required: ['id']
      }
    }
  • Core implementation of stopTimer: performs DELETE request to FreeAgent API endpoint /timeslips/{id}/timer to stop the running timer and returns the updated Timeslip.
    async stopTimer(id: string): Promise<Timeslip> {
        try {
            console.error('[API] Stopping timer for timeslip:', id);
            const response = await this.axiosInstance.delete<TimeslipResponse>(`/timeslips/${id}/timer`);
            return response.data.timeslip;
        } catch (error) {
            console.error('[API] Failed to stop 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 full burden for behavioral disclosure. It states the action ('Stop') but doesn't clarify whether this is a mutation (likely yes), what permissions are required, if it's idempotent, what happens on success/failure, or any side effects. The description is minimal and lacks critical behavioral context.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized and front-loaded, with zero wasted text.

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 no annotations and no output schema, the description is incomplete for a mutation tool. It doesn't explain what happens after stopping the timer (e.g., does it return the stopped timeslip? update a status field?), nor does it cover error conditions or behavioral traits. The minimal description leaves significant gaps.

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?

The input schema has 100% description coverage, with the single parameter 'id' documented as 'Timeslip ID'. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without adding value.

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 ('Stop') and target resource ('a running timer for a timeslip'), which distinguishes it from siblings like 'start_timer' or 'delete_timeslip'. However, it doesn't specify what 'timeslip' refers to in this context, leaving some ambiguity about the resource scope.

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 'update_timeslip' or 'delete_timeslip'. It doesn't mention prerequisites (e.g., only works if a timer is currently running) or exclusions, leaving the agent to infer usage from the tool name alone.

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