Feature Request: Project result reports — hours, costs, and revenue per project per period (resultatrapport)

Current state

The Tripletex MCP server provides good granular access to projects
(search_projects), hour entries (search_timesheet_entries), supplier invoices,
and overall timesheet management. However, there is currently no convenient way
to retrieve a consolidated project result report (resultatrapport) for a given
project over a period.

Today an assistant can:

• List projects and hour entries
• Search invoices and supplier invoices

…but must manually combine these sources to calculate revenue vs. costs, gross
margin, and total hours for a project in a specific period. There is no single
call that returns the aggregated financial performance of a project.

Requested tools

• get_project_result_report(projectId, dateFrom, dateTo) — Consolidated report
  for one project in the period containing:

  • Total revenue / invoiced amount
  • Total costs booked (from ledger / supplier invoices)
  • Registered hours (from timesheet entries)
  • Gross margin / result
  • Optional breakdown by activity, employee, or cost type

• search_project_result_reports(dateFrom, dateTo, projectIds?, customerId?) —
  Result reports for multiple projects in the period (for monthly/periodic
  reporting across a portfolio)

• get_project_hours_summary(projectId, dateFrom, dateTo) — Aggregated hours
  per employee/activity for the period (more convenient than manually paging
  through search_timesheet_entries)

• get_project_cost_summary(projectId, dateFrom, dateTo) — Aggregated costs
  by account/supplier for the period

Why this matters

In Norwegian construction and project-based companies, the resultatrapport is
one of the most frequently used reports for project managers and controllers.
Being able to fetch it programmatically would let AI assistants:

• Generate monthly project status reports automatically
• Compare actual vs. budget (prognose) without the user opening Tripletex
• Surface overruns early (e.g. "Project 4333 is 12 % over budget on costs this
  month")
• Support the existing budget/prognose routines that many teams already run
  twice a year

The underlying Tripletex REST API already contains the necessary data. This
request is about surfacing the aggregated view through the MCP in the same
clean, consistent style as the existing read tools.

Additional notes

• Access control should follow the same rules as the existing hour and invoice
  tools (department/project restrictions).
• Date range should follow the inclusive start / exclusive end convention used
  by the existing tools.
• Returning both a human-readable summary and a structured JSON object would be
  useful for assistants.

Thank you for the great work on this MCP server — it's already very useful, and
closing this gap would make it even more powerful for project-based companies.

Start by reviewing the existing search_projects, search_timesheet_entries, invoice, and supplier-invoice tools and the Tripletex REST API report endpoints they use. Define the scope and response shape for the requested project result, hours, and cost summaries, then verify date boundaries and access-control behavior; done means the selected report tools return the requested aggregated fields for the specified period.