Skip to main content
Glama

get_timeslip

Retrieve a specific timeslip from FreeAgent using its unique ID to access time tracking details for billing or reporting purposes.

Instructions

Get a single timeslip by ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesTimeslip ID

Implementation Reference

  • Handler for the get_timeslip tool that extracts the ID from arguments and delegates to FreeAgentClient.getTimeslip, returning JSON response.
    case 'get_timeslip': {
      const { id } = request.params.arguments as { id: string };
      const timeslip = await this.client.getTimeslip(id);
      return {
        content: [{ type: 'text', text: JSON.stringify(timeslip, null, 2) }]
      };
    }
  • src/index.ts:106-116 (registration)
    Tool registration in ListTools handler, defining name, description, and input schema requiring 'id'.
    {
      name: 'get_timeslip',
      description: 'Get a single timeslip by ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Timeslip ID' }
        },
        required: ['id']
      }
    },
  • Implementation of getTimeslip in FreeAgentClient, performs API GET request to retrieve timeslip by ID.
    async getTimeslip(id: string): Promise<Timeslip> {
        try {
            console.error('[API] Fetching timeslip:', id);
            const response = await this.axiosInstance.get<TimeslipResponse>(`/timeslips/${id}`);
            return response.data.timeslip;
        } catch (error) {
            console.error('[API] Failed to fetch timeslip:', error);
            throw error;
        }
    }
  • Type schemas for API response (TimeslipResponse) and Timeslip object used in getTimeslip.
    export interface TimeslipResponse {
        timeslip: Timeslip;
    }
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 tool retrieves data ('Get'), implying a read-only operation, but fails to specify critical details like whether authentication is required, if there are rate limits, error handling for invalid IDs, or the format of the returned data. This leaves significant gaps in understanding the tool's behavior.

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 is front-loaded and wastes no space, making it easy for an agent to parse quickly.

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 lack of annotations and output schema, the description is incomplete for a tool that retrieves data. It does not explain what a 'timeslip' is, what data is returned, or any behavioral constraints, leaving the agent with insufficient context to use the tool effectively beyond basic parameter input.

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 clearly documented as 'Timeslip ID'. The description adds no additional meaning beyond this, as it merely restates the parameter's purpose without providing context like ID format or examples. Given the high schema coverage, a 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 clearly states the action ('Get') and resource ('a single timeslip by ID'), making the purpose unambiguous. It distinguishes from siblings like 'list_timeslips' by specifying retrieval of a single item rather than multiple, though it doesn't explicitly contrast with other read operations like 'list_timeslips' beyond the scope difference.

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 'list_timeslips' or other siblings. It lacks context such as prerequisites (e.g., needing an existing timeslip ID) or exclusions, leaving the agent to infer usage based on 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