Skip to main content
Glama

generate-report

Generate comprehensive reports and analytics from Float data. Covers time tracking, project performance, resource utilization, budget analysis, and team metrics with flexible filters and formats.

Instructions

Consolidated tool for generating comprehensive reports and analytics from Float data. Supports various report types including time tracking, project performance, resource utilization, budget analysis, and team metrics with flexible filtering and formatting options.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
activeNoFilter by active status (0=archived, 1=active)
formatNoResponse format - either "json" or "xml"json
statusNoFilter by status
billableNoFilter by billable status (0=non-billable, 1=billable)
end_dateNoEnd date for report data (YYYY-MM-DD)
group_byNoGroup report data by specified field
client_idNoFilter by specific client ID
people_idNoFilter by specific person ID
project_idNoFilter by specific project ID
start_dateNoStart date for report data (YYYY-MM-DD)
report_typeYesThe type of report to generate
time_periodNoTime period aggregation
department_idNoFilter by specific department ID
report_formatNoOutput format for the report (json, csv, xml)json
forecast_weeksNoNumber of weeks to forecast capacity
include_totalsNoInclude totals and summaries
include_detailsNoInclude detailed breakdown in report
exclude_holidaysNoExclude holidays from utilization calculations
exclude_weekendsNoExclude weekends from utilization calculations
capacity_thresholdNoCapacity threshold percentage
include_percentagesNoInclude percentage calculations
target_hours_per_dayNoTarget hours per day for utilization calculations
compare_previous_periodNoInclude comparison with previous period
include_budget_varianceNoInclude budget variance analysis
budget_warning_thresholdNoBudget warning threshold percentage
Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It says 'generating' but doesn't clarify if this is a read-only operation, side effects, or required permissions. This is inadequate for a mutation-like verb.

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 a single, concise sentence but lacks structure for a complex 25-parameter tool. It is front-loaded but omits critical details, making it somewhat under-specified.

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 tool's complexity (25 parameters, no output schema) and the presence of many sibling get-* tools, the description is insufficient. It doesn't explain how report_type selects different behaviors or how parameters interact, leaving the agent underinformed.

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

Parameters3/5

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

With 100% schema coverage, all parameters have descriptions, so the baseline is 3. The description adds only generic context about filtering and formatting, adding no specific semantic value beyond what the schema already provides.

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 the tool generates comprehensive reports and analytics from Float data, listing several report types. It distinguishes from siblings by being a consolidated tool, though it could more explicitly state that it combines multiple report types.

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 explicit guidance on when to use this consolidated tool versus the specific get-* report siblings. The description lacks context about use cases and alternatives, leaving the agent to infer from tool names.

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/asachs01/float-mcp'

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