Skip to main content
Glama
standardbeagle

Harvest MCP Server

version

Check the current version of the Harvest MCP server to verify compatibility and access time tracking features.

Instructions

Get version information about the Harvest MCP server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • MCP server handler for the 'version' tool that calls harvestClient.getVersion() and returns the version information as text content.
    case 'version':
      const versionInfo = harvestClient.getVersion();
      return {
        content: [
          {
            type: 'text',
            text: versionInfo,
          },
        ],
      };
  • Schema definition for the 'version' tool, specifying name, description, and empty input schema. This is part of the tools array used for tool listing.
    {
      name: 'version',
      description: 'Get version information about the Harvest MCP server.',
      inputSchema: {
        type: 'object',
        properties: {}
      }
    },
  • Helper method getVersion() in HarvestClient that returns a formatted JSON object with version details of the MCP server and Harvest API.
    // Version Information
    getVersion(): string {
      return JSON.stringify({
        name: '@standardbeagle/harvest-mcp',
        version: '0.2.0',
        description: 'Model Context Protocol server for Harvest API integration',
        author: 'standardbeagle',
        license: 'MIT',
        repository: 'https://github.com/standardbeagle/harvest-mcp',
        mcpVersion: '2025-06-18',
        harvestApiVersion: 'v2'
      }, null, 2);
    }
Behavior4/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It clearly indicates this is a read-only operation ('Get') that returns information, not a mutation. However, it doesn't specify response format, error conditions, or rate limits, leaving some behavioral aspects undocumented.

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 communicates the complete purpose without any wasted words. It's appropriately sized for a simple tool and front-loads the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter tool with no output schema, the description provides adequate context about what information is retrieved. However, it doesn't specify what 'version information' includes (e.g., server version, API version, build date), leaving some ambiguity about the return value.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't discuss parameters since none exist, earning a baseline score of 4 for zero-parameter tools.

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

Purpose5/5

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

The description clearly states the specific action ('Get') and resource ('version information about the Harvest MCP server'), distinguishing it from sibling tools like 'about' or other Harvest-specific operations. It precisely communicates what the tool does without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving server version information, but provides no explicit guidance on when to use this tool versus alternatives like 'about' or other system-info tools. Usage context is inferred rather than stated, leaving some ambiguity.

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