Skip to main content
Glama
Stefan39

mite

by Stefan39
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Billable and non-billable hours with billable share

mite_report_billable_ratio
Read-only

Calculate billable and non-billable hours plus the billable share percentage for a chosen period, optionally grouped by customer, project, user, or month.

Instructions

Billable hours, non-billable hours and the billable share in percent for a period, optionally per customer, project, user, month, aggregated on the mite server. For revenue or other groupings use mite_report. Returns hours and a ratio in percent with one decimal, per group and as a total. Read-only, no paging, default period is this year.

Input Schema

NameRequiredDescriptionDefault
toNoEnd of the period: a date as YYYY-MM-DD (e.g. 2026-03-31) or a keyword (today, yesterday, this_week, last_week, this_month, last_month, this_year, last_year). Default: today when only from is a date; without from the period is just this date.
fromNoStart of the period: a date as YYYY-MM-DD (e.g. 2026-01-01) or a keyword (today, yesterday, this_week, last_week, this_month, last_month, this_year, last_year). A keyword alone selects that whole period and ignores the end of it; a date alone runs up to today. Default: this_year (when from and to are both omitted).
group_byNoOne of: customer, project, user, month, e.g. "customer". Default: only the total, no rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.1
    • changedInput schema / properties / from / description
      Previous value: -"Start date (YYYY-MM-DD) or a keyword such as this_month. Default: this_year."New value: +"Start of the period: a date as YYYY-MM-DD (e.g. 2026-01-01) or a keyword (today, yesterday, this_week, last_week, this_month, last_month, this_year, last_year). A keyword alone selects that whole period and ignores the end of it; a date alone runs up to today. Default: this_year (when from and to are both omitted)."
    • changedInput schema / properties / group_by / description
      Previous value: -"One of: customer, project, user, month. Default: only the total."New value: +"One of: customer, project, user, month, e.g. \"customer\". Default: only the total, no rows."
    • changedInput schema / properties / to / description
      Previous value: -"End date (YYYY-MM-DD) or a keyword. Default: the end of the period given in from."New value: +"End of the period: a date as YYYY-MM-DD (e.g. 2026-03-31) or a keyword (today, yesterday, this_week, last_week, this_month, last_month, this_year, last_year). Default: today when only from is a date; without from the period is just this date."
  2. First observedv1.0.0

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the `readOnlyHint`, the description provides several vital operational constraints, including 'no paging,' the precise output format ('hours and a ratio in percent with one decimal'), and the 'default period is this year.'

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 definition is extremely concise. It packs the resource name, core metrics, aggregation level, operational constraints, and sibling differentiation into a tightly written, single block of text.

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?

Given that the schema is complete (100% coverage), the description covers all remaining high-value information: aggregation level, output formatting (one decimal), lack of pagination, and default temporal scope.

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

Parameters4/5

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

While the schema covers the parameter types, the description adds semantic value by confirming the granularity of the output (per group and as a total) and the default scope of the period (this year).

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 is highly specific, stating it reports 'billable hours, non-billable hours and the billable share in percent.' Furthermore, it clearly differentiates itself from the general 'mite_report' sibling by specifying the focus on billability ratios.

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

Usage Guidelines5/5

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

Usage guidance is excellent because it provides a direct comparative rule: 'For revenue or other groupings use `mite_report`.' This gives the agent an explicit alternative choice for related queries.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools