Skip to main content
Glama
AZX-PBC-OSS

harvest-forecast-mcp

by AZX-PBC-OSS

who_is_available

Find people with available capacity by checking if their scheduled allocation stays below a daily threshold within a date range.

Instructions

Find people who have capacity (are not fully scheduled) in a date range.

Lists Forecast people whose total scheduled allocation in the period
is below the given threshold, so they can take on more work.

Args:
    start_date: Start of date range (YYYY-MM-DD).
    end_date: End of date range (YYYY-MM-DD).
    max_daily_minutes: Max allocation to be considered "available" (default 480 = 8h/day).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_dateYes
start_dateYes
max_daily_minutesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It clearly describes the behavior as a query that checks allocation against a threshold, though it lacks details on data recency or permissions.

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 concise with a clear purpose statement, a sentence on functionality, and an Args list. Every element is necessary and front-loaded.

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

Completeness5/5

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

The description is complete for a query tool with an output schema. It covers all parameters, the threshold logic, and the goal, making it self-sufficient.

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% but description thoroughly explains each parameter, including start_date, end_date, and max_daily_minutes with default, adding meaning beyond the schema.

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 tool's purpose: finding people with capacity by comparing scheduled allocation to a threshold, which distinguishes it from siblings like 'person_schedule' or 'team_utilization'.

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

Usage Guidelines4/5

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

The description explains when to use the tool (to find people available for more work), but does not explicitly mention when not to use or alternatives, though sibling context provides differentiation.

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