Skip to main content
Glama
AZX-PBC-OSS

harvest-forecast-mcp

by AZX-PBC-OSS
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

get_person_heatmap

Retrieve a scheduling heatmap for a specific person within a date range, showing daily or weekly workload intensity.

Instructions

Get a scheduling heatmap for a Forecast person.

Args:
    person_id: Forecast person ID.
    from_date: Start date (YYYY-MM-DD).
    to_date: End date (YYYY-MM-DD).
    scale: Time scale — "daily" or "weekly".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNodaily
to_dateYes
from_dateYes
person_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

C2.7/5.0
Behavior1/5

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

No annotations are provided, and the description lacks any behavioral traits such as effects of invalid inputs, rate limits, caching, or response format. The description carries the full burden but discloses no behavioral details.

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 short and to the point, but it is under-specified. It is concise but lacks necessary detail, making it minimally acceptable.

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 the complexity (4 params, no annotations, output schema exists but unused), the description is incomplete. It does not explain the heatmap concept or provide usage context, leaving significant gaps.

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

Parameters2/5

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

Schema description coverage is 0%, and the description merely lists parameter names without adding meaning beyond the schema. It does not explain what a 'heatmap' is, the date format, or how 'scale' affects output.

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 gets a scheduling heatmap for a Forecast person, using a specific verb and resource. It effectively distinguishes from sibling tools like get_project_heatmap and get_placeholder_heatmap by specifying the target is a person.

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?

There is no guidance on when to use this tool versus alternatives. No information about prerequisites, context, or exclusions is 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