Skip to main content
Glama

get-project-report

Get a project summary report with filters for date range, project ID, client ID, and status to track project performance.

Instructions

Get project summary report

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_dateNoStart date for report (YYYY-MM-DD)
end_dateNoEnd date for report (YYYY-MM-DD)
project_idNoFilter by project ID
client_idNoFilter by client ID
statusNoFilter by project status

Implementation Reference

  • The getProjectReport tool handler - calls Float API /reports/projects endpoint with optional filters (start_date, end_date, project_id, client_id, status) and returns project summary data including name, client_id, status, total_hours, billable_hours, budget, and budget_used.
    // Get project report
    export const getProjectReport = createTool(
      'get-project-report',
      'Get project summary report',
      z.object({
        start_date: z.string().optional().describe('Start date for report (YYYY-MM-DD)'),
        end_date: z.string().optional().describe('End date for report (YYYY-MM-DD)'),
        project_id: z.number().optional().describe('Filter by project ID'),
        client_id: z.number().optional().describe('Filter by client ID'),
        status: z.number().optional().describe('Filter by project status'),
      }),
      async (params) => {
        const response = await floatApi.getPaginated(
          '/reports/projects',
          params,
          z.array(
            z.object({
              project_id: z.number().optional(),
              name: z.string().optional(),
              client_id: z.number().optional(),
              status: z.number().optional(),
              total_hours: z.number().optional(),
              billable_hours: z.number().optional(),
              budget: z.number().optional(),
              budget_used: z.number().optional(),
            })
          )
        );
        return response;
      }
    );
  • Input schema for getProjectReport: start_date (optional string), end_date (optional string), project_id (optional number), client_id (optional number), status (optional number).
    z.object({
      start_date: z.string().optional().describe('Start date for report (YYYY-MM-DD)'),
      end_date: z.string().optional().describe('End date for report (YYYY-MM-DD)'),
      project_id: z.number().optional().describe('Filter by project ID'),
      client_id: z.number().optional().describe('Filter by client ID'),
      status: z.number().optional().describe('Filter by project status'),
  • Output/response schema for getProjectReport: array of objects with project_id, name, client_id, status, total_hours, billable_hours, budget, budget_used.
    z.array(
      z.object({
        project_id: z.number().optional(),
        name: z.string().optional(),
        client_id: z.number().optional(),
        status: z.number().optional(),
        total_hours: z.number().optional(),
        billable_hours: z.number().optional(),
        budget: z.number().optional(),
        budget_used: z.number().optional(),
      })
    )
  • Import and registration of getProjectReport: imported from './reporting/reports.js' and added to the legacyTools array (line 313) which is then exported as part of the 'tools' array (line 319).
    // Reporting tools
    import {
      getTimeReport,
      getProjectReport,
      getPeopleUtilizationReport,
    } from './reporting/reports.js';
    
    // Legacy tools export (preserved for backward compatibility)
    export const legacyTools = [
  • The createTool helper function used to define getProjectReport. It wraps the handler with input validation (Zod schema parsing), error handling (FloatApiError, ZodError, general errors), and response formatting.
    export const createTool = <T, P extends z.ZodType>(
      name: string,
      description: string,
      schema: P,
      handler: (params: z.infer<P>) => Promise<T>
    ): {
      name: string;
      description: string;
      inputSchema: P;
      handler: (params: unknown) => Promise<ToolResponse<T>>;
    } => {
      return {
        name,
        description,
        inputSchema: schema,
        handler: async (params: unknown): Promise<ToolResponse<T>> => {
          try {
            const validatedParams = schema.parse(params);
            const result = await handler(validatedParams);
    
            // Extract format from params if available
            const responseFormat =
              ((validatedParams as Record<string, unknown>).format as ResponseFormat) || 'json';
    
            return { success: true, data: result, format: responseFormat };
          } catch (error) {
            logger.error(`Error in ${name} tool:`, error);
    
            // Handle Float API errors with enhanced formatting
            if (error instanceof FloatApiError) {
              return FloatErrorHandler.formatErrorForMcp(error) as ToolResponse<T>;
            }
    
            // Handle parameter validation errors
            if (error instanceof z.ZodError) {
              return {
                success: false,
                error: `Parameter validation failed: ${error.errors.map((e) => `${e.path.join('.')}: ${e.message}`).join(', ')}`,
                errorCode: 'PARAMETER_VALIDATION_ERROR',
                details: {
                  validationErrors: error.errors,
                },
              } as ToolResponse<T>;
            }
    
            // Handle other errors
            return {
              success: false,
              error: error instanceof Error ? error.message : 'Unknown error occurred',
              errorCode: 'UNKNOWN_ERROR',
            } as ToolResponse<T>;
          }
        },
      };
    };
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits such as read-only nature, access requirements, or output characteristics. The minimal description fails to compensate for missing annotations.

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

Conciseness2/5

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

The description is extremely concise at 3 words, but lacks necessary detail, making it under-specified rather than efficiently focused.

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?

With no output schema and vague description, the tool is incomplete for an agent to understand what the report contains. The optional parameters suggest filtering but no hint of report content.

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?

The input schema provides 100% coverage with descriptions for all 5 parameters, so the description need not add further details. However, it adds no contextual value about parameter interactions or usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get project summary report' states the verb and resource but lacks specificity on what data is summarized. Compared to sibling tools like 'get-project-logged-time-summary', it does not differentiate itself clearly.

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 guidance on when to use this tool versus alternatives like 'get-billable-time-report' or 'get-project-logged-time-summary'. The absence of usage context makes it hard for an agent to choose correctly.

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