Skip to main content
Glama
standardbeagle

Harvest MCP Server

harvest_get_project

Retrieve detailed information about a specific project from Harvest time tracking system by providing its unique project ID.

Instructions

Get details of a specific project. Use about {"tool": "harvest_get_project"} for detailed usage examples.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProject ID

Implementation Reference

  • Core handler function that executes the Harvest API request to retrieve details of a specific project by ID.
    async getProject(id: string) {
      return this.makeRequest(`/projects/${id}`);
    }
  • MCP tool call dispatcher case that invokes the HarvestClient.getProject method and formats the JSON response.
    case 'harvest_get_project':
      const project = await harvestClient.getProject(typedArgs.id as string);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(project, null, 2),
          },
        ],
      };
  • Defines the tool's metadata, description, and input schema requiring a 'id' parameter of type string.
    {
      name: 'harvest_get_project',
      description: 'Get details of a specific project. Use about {"tool": "harvest_get_project"} for detailed usage examples.',
      inputSchema: {
        type: 'object',
        properties: {
          id: { type: 'string', description: 'Project ID' }
        },
        required: ['id']
      }
    },
  • src/index.ts:69-73 (registration)
    Registers the list tools handler which returns the tools array including harvest_get_project schema.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: tools,
      };
    });
  • Generic HTTP request helper used by getProject to make authenticated API calls to Harvest.
    private async makeRequest(endpoint: string, options: RequestInit = {}) {
      const url = `${this.baseUrl}${endpoint}`;
      
      const response = await fetch(url, {
        ...options,
        headers: {
          'Authorization': `Bearer ${this.accessToken}`,
          'Harvest-Account-ID': this.accountId,
          'User-Agent': this.userAgent,
          'Content-Type': 'application/json',
          ...options.headers,
        },
      });
    
      if (!response.ok) {
        let errorMessage = `Harvest API error: ${response.status} ${response.statusText}`;
        
        try {
          const errorBody = await response.json() as any;
          if (errorBody.message) {
            errorMessage += ` - ${errorBody.message}`;
          }
        } catch {
          // If we can't parse the error response, use the basic error message
        }
        
        throw new Error(errorMessage);
      }
    
      return response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get details' but doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what details are returned. This leaves significant gaps for a read operation.

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 includes a second sentence referencing another tool for examples, which adds minimal value and could be considered redundant. It's front-loaded with the core purpose but not optimally concise.

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. It doesn't explain what details are returned, error cases, or prerequisites, making it inadequate for a tool that fetches project data without structured output documentation.

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?

Schema description coverage is 100%, so the schema already documents the 'id' parameter. The description adds no additional meaning beyond what the schema provides, such as format examples or constraints, meeting the baseline for high coverage.

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 verb 'Get' and resource 'details of a specific project', making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'harvest_list_projects' or 'harvest_list_project_assignments', which would require a 5.

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 'harvest_list_projects' for listing multiple projects. It only references another tool 'about' for examples, which doesn't clarify usage 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/standardbeagle/harvest-mcp'

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