Skip to main content
Glama
adrian-dotco

Harvest Natural Language Time Entry MCP Server

by adrian-dotco

list_entries

Retrieve recent time entries from Harvest by specifying date ranges to review tracked work hours and activities.

Instructions

List recent time entries

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoStart date (YYYY-MM-DD)
toNoEnd date (YYYY-MM-DD)

Implementation Reference

  • Handler for the 'list_entries' tool. Extracts optional 'from' and 'to' dates from arguments, queries the Harvest API for time entries, maps the response to a simplified format, and returns it as JSON text content.
    case 'list_entries': {
      const { from, to } = request.params.arguments as { from?: string; to?: string };
      const params: Record<string, string> = {};
      if (from) params.from = from;
      if (to) params.to = to;
      
      const response = await this.axiosInstance.get('/time_entries', { params });
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(response.data.time_entries.map((e: { id: number; spent_date: string; hours: number; notes: string; project: { name: string }; task: { name: string } }) => ({
              id: e.id,
              spent_date: e.spent_date,
              hours: e.hours,
              notes: e.notes,
              project: e.project.name,
              task: e.task.name,
            })), null, 2),
          },
        ],
      };
    }
  • src/index.ts:303-318 (registration)
    Registration of the 'list_entries' tool in the tools array, including its name, description, and input schema definition.
      name: 'list_entries',
      description: 'List recent time entries',
      inputSchema: {
        type: 'object',
        properties: {
          from: {
            type: 'string',
            description: 'Start date (YYYY-MM-DD)',
          },
          to: {
            type: 'string',
            description: 'End date (YYYY-MM-DD)',
          },
        },
      },
    },
  • Input schema for the 'list_entries' tool defining optional 'from' and 'to' date parameters.
    inputSchema: {
      type: 'object',
      properties: {
        from: {
          type: 'string',
          description: 'Start date (YYYY-MM-DD)',
        },
        to: {
          type: 'string',
          description: 'End date (YYYY-MM-DD)',
        },
      },
    },
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 a read operation ('List') but lacks details on permissions, pagination, rate limits, or what 'recent' entails. This is inadequate for a tool with potential behavioral nuances.

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 appropriately sized and front-loaded, making it easy to scan and understand the core purpose immediately.

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, no output schema, and a simple input schema, the description is incomplete. It doesn't address behavioral aspects like return format, error handling, or how it differs from siblings, leaving gaps for an AI agent to understand full context.

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 schema description coverage is 100%, with clear descriptions for 'from' and 'to' parameters. The description adds no additional meaning beyond the schema, as it doesn't explain how 'recent' relates to the date range or provide usage examples. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List recent time entries' states a clear verb ('List') and resource ('time entries'), but lacks specificity about scope or differentiation from siblings like 'get_time_report' or 'log_time'. It's vague about what 'recent' means compared to the date parameters in the schema.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_time_report' (which might offer more detailed reporting) or 'log_time' (for creating entries). The description implies a basic listing function but offers no explicit context or exclusions.

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/adrian-dotco/harvest-mcp-server'

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