Skip to main content
Glama
AZX-PBC-OSS

harvest-forecast-mcp

by AZX-PBC-OSS

list_time_entries

Retrieve time entries from Harvest filtered by user, project, and date range. Get a list of tracked hours for specific periods or projects.

Instructions

List time entries from Harvest, optionally filtered by user, project, and date range.

Args:
    user_id: Filter to a specific user's entries.
    project_id: Filter to a specific project's entries.
    from_date: Start date (YYYY-MM-DD). Defaults to 30 days ago.
    to_date: End date (YYYY-MM-DD). Defaults to today.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_dateNo
user_idNo
from_dateNo
project_idNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions filtering and defaults but omits details like read-only nature, pagination, or rate limits.

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

Conciseness4/5

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

The description is concise and front-loaded, using a clear docstring format. However, it could be slightly more terse by avoiding the 'Args' section repetition.

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

Completeness3/5

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

Given no output schema for return values is required, but the description lacks details on result ordering, pagination, or volume limits. It is adequate but leaves gaps for a complete picture.

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?

With 0% schema coverage, the description adds meaning by explaining each parameter's purpose and defaults (e.g., from_date defaults to 30 days ago). This significantly aids agent understanding.

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 it lists time entries from Harvest with optional filters. It distinguishes from sibling tools by specifying 'time entries' rather than projects or tasks.

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 does not provide guidance on when to use this tool versus alternatives (e.g., create_time_entry for adding entries). No usage context or exclusions are given.

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/AZX-PBC-OSS/harvest-forecast-mcp'

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