Skip to main content
Glama

delete_timeslip

Remove a specific timeslip record from your FreeAgent account by providing its ID to manage time tracking data.

Instructions

Delete a timeslip

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTimeslip ID

Implementation Reference

  • Core handler function that executes the DELETE request to the FreeAgent API to delete the timeslip by ID.
    async deleteTimeslip(id: string): Promise<void> {
        try {
            console.error('[API] Deleting timeslip:', id);
            await this.axiosInstance.delete(`/timeslips/${id}`);
        } catch (error) {
            console.error('[API] Failed to delete timeslip:', error);
            throw error;
        }
    }
  • MCP server handler that extracts the ID from tool arguments and delegates to FreeAgentClient.deleteTimeslip.
    case 'delete_timeslip': {
      const { id } = request.params.arguments as { id: string };
      await this.client.deleteTimeslip(id);
      return {
        content: [{ type: 'text', text: 'Timeslip deleted successfully' }]
      };
    }
  • Tool schema definition including input schema requiring 'id' string, provided in ListTools response.
    {
      name: 'delete_timeslip',
      description: 'Delete a timeslip',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Timeslip ID' }
        },
        required: ['id']
      }
    },
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 'Delete a timeslip', implying a destructive mutation, but doesn't specify if deletion is permanent, reversible, requires specific permissions, or has side effects. This is a significant gap for a destructive tool with zero annotation coverage.

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 waste. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place without redundancy.

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 tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral risks, return values, or error conditions. For a mutation tool with high stakes, more context is needed to ensure safe and correct usage.

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 'id' parameter documented as 'Timeslip ID'. The description adds no additional meaning beyond this, such as format examples or sourcing instructions. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

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 'Delete a timeslip' clearly states the verb (delete) and resource (timeslip), making the purpose immediately understandable. It distinguishes from siblings like create_timeslip, get_timeslip, and update_timeslip by specifying the destructive action. However, it doesn't specify what a timeslip is or its scope, keeping it from a perfect score.

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. It doesn't mention prerequisites (e.g., needing an existing timeslip ID), exclusions, or comparisons to siblings like update_timeslip for modifications. This leaves the agent without context for tool selection.

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