Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_list_project_assignments

Retrieve your assigned projects from Harvest to track time and manage tasks effectively.

Instructions

List project assignments for the current user. Use about {"tool": "harvest_list_project_assignments"} for detailed usage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
per_pageNoResults per page (max 100)

Implementation Reference

  • Core handler function that executes the tool logic by making the Harvest API request to /users/me/project_assignments with optional pagination parameters.
    async getProjectAssignments(options?: any) {
      const queryString = this.buildQueryString(options);
      return this.makeRequest(`/users/me/project_assignments${queryString}`);
    }
  • MCP server tool call handler that delegates to HarvestClient and formats the JSON response.
    case 'harvest_list_project_assignments':
      const projectAssignments = await harvestClient.getProjectAssignments(typedArgs);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(projectAssignments, null, 2),
          },
        ],
      };
  • Tool schema definition including name, description, and input validation schema.
      name: 'harvest_list_project_assignments',
      description: 'List project assignments for the current user. Use about {"tool": "harvest_list_project_assignments"} for detailed usage.',
      inputSchema: {
        type: 'object',
        properties: {
          page: { type: 'number', description: 'Page number' },
          per_page: { type: 'number', description: 'Results per page (max 100)' }
        }
      }
    },
  • src/index.ts:69-73 (registration)
    Registers the list of tools (including this one) for the MCP server.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: tools,
      };
    });
  • Detailed documentation string for the tool, used by the 'about' tool.
          'harvest_list_project_assignments': `# harvest_list_project_assignments
    
    Lists project assignments for the current user.
    
    ## Purpose
    See which projects you have access to and can log time against.
    
    ## Parameters
    - \`page\` (number, optional): Page number for pagination
    - \`per_page\` (number, optional): Results per page, max 100
    
    ## Example Usage
    
    **List your project assignments:**
    \`\`\`json
    {
      "tool": "harvest_list_project_assignments"
    }
    \`\`\`
    
    **With pagination:**
    \`\`\`json
    {
      "tool": "harvest_list_project_assignments",
      "page": 1,
      "per_page": 25
    }
    \`\`\`
    
    ## Response Format
    Returns object with:
    - \`project_assignments\`: Array of assignment objects
    - Pagination information
    
    Each assignment includes:
    - \`id\`: Assignment ID
    - \`project\`: Full project object  
    - \`client\`: Full client object
    - \`hourly_rate\`: Your rate for this project
    - \`budget\`: Budget information
    - \`is_active\`: Assignment status
    - \`created_at\`, \`updated_at\`: Timestamps
    
    ## Usage Tips
    - Essential for finding valid project_id values for time entries
    - Shows your specific hourly rate per project
    - Use with harvest_list_task_assignments to get complete assignment info`,
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions listing assignments but fails to describe key behaviors: it doesn't specify if this is a read-only operation (implied but not stated), how pagination works with the 'page' and 'per_page' parameters, what the output format looks like, or any rate limits or authentication requirements. The reference to another tool for 'detailed usage' is vague and unhelpful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief but inefficiently structured. The first sentence is clear, but the second sentence ('Use about...') is redundant and doesn't add value for an AI agent, as it references an external tool without context. This wastes space that could be used for more useful information, such as behavioral details or usage guidelines.

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 complexity (a list operation with pagination parameters) and the lack of annotations and output schema, the description is incomplete. It doesn't explain the return values, pagination behavior, or how to interpret results. The reference to another tool for 'detailed usage' is insufficient, leaving gaps that could hinder an AI agent's ability to use this tool effectively.

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 clear documentation for 'page' and 'per_page' parameters. The description adds no additional semantic information about these parameters beyond what the schema provides. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 tool's purpose: 'List project assignments for the current user.' It specifies the verb ('List'), resource ('project assignments'), and scope ('for the current user'). However, it doesn't explicitly distinguish this tool from similar siblings like 'harvest_list_projects' or 'harvest_list_task_assignments', which could cause confusion about what exactly is being listed.

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 minimal usage guidance. It only references using another tool ('about') for detailed usage, which is not helpful for an AI agent deciding when to invoke this tool. There's no explicit guidance on when to use this tool versus alternatives like 'harvest_list_projects' or 'harvest_list_task_assignments', nor any context about prerequisites or typical use cases.

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/standardbeagle/harvest-mcp'

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