Skip to main content
Glama
AZX-PBC-OSS

harvest-forecast-mcp

by AZX-PBC-OSS
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

create_assignment

Schedule a person on a Forecast project by providing project ID, person ID, start and end dates, and optional daily allocation and notes.

Instructions

Schedule a person on a Forecast project.

Args:
    project_id: Forecast project ID (must be >= 1).
    person_id: Forecast person ID (0 = Everyone).
    start_date: Assignment start date (YYYY-MM-DD).
    end_date: Assignment end date (YYYY-MM-DD).
    allocation: Allocation in minutes per day (e.g. 480 = 8 hours).
    notes: Optional notes for the assignment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNo
end_dateYes
person_idYes
allocationNo
project_idYes
start_dateYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A3.5/5.0
Behavior2/5

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

No annotations exist, so description must disclose behavior. It lists parameters but does not mention side effects, permissions, idempotency, or error handling. The existence of an output schema is not reflected in the description.

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 front-loaded with the purpose and uses a clear bullet list. It is concise, though the 'Args:' block could be slightly more compact.

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?

Parameter documentation is complete, but the description lacks any guidance on return values, error conditions, or prerequisites. The output schema exists but is not referenced.

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

Parameters5/5

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

Schema coverage is 0%, and the description thoroughly explains each parameter's meaning and constraints, such as project_id >= 1, person_id (0 = Everyone), date format, allocation in minutes, and optional notes.

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 starts with a clear action and resource: 'Schedule a person on a Forecast project.' This distinguishes it from sibling tools like list_assignments, delete_assignment, and update_assignment.

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 mention of when to use this tool versus alternatives like update_assignment or delete_assignment. No prerequisites or usage context provided.

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