Skip to main content
Glama
Stefan39

mite

by Stefan39
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Hours and revenue per project and month

mite_report_projects_by_month
Read-only

Generates monthly hours and revenue totals per project for a selected period, enabling review of annual project performance without listing individual time entries.

Instructions

Aggregated report from mite: hours and revenue per project and month for a period, grouped on the mite server so whole years work without reading single entries. For other groupings or totals use mite_report; for single entries use mite_list_time_entries. Returns rows of month (YYYY-MM), project, hours and revenue in currency units plus a total; revenue is null without rates. 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).
user_idNoOnly these users: list of mite user ids, e.g. [7]. Needs an API key that may see other users. Default: all users the key may see.
billableNotrue = only billable entries, false = only non-billable entries. Default: both.
project_idNoOnly these projects: list of mite project ids, e.g. [789]. Default: all projects.
service_idNoOnly these services: list of mite service ids, e.g. [42]. Default: all services.
customer_idNoOnly these customers: list of mite customer ids, e.g. [123, 456]. Default: all customers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.0.1
    • changedInput schema / properties / billable / description
      Previous value: -"true = only billable, false = only non-billable."New value: +"true = only billable entries, false = only non-billable entries. Default: both."
    • changedInput schema / properties / customer_id / description
      Previous value: -"Only these customers."New value: +"Only these customers: list of mite customer ids, e.g. [123, 456]. Default: all customers."
    • 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 / project_id / description
      Previous value: -"Only these projects."New value: +"Only these projects: list of mite project ids, e.g. [789]. Default: all projects."
    • changedInput schema / properties / service_id / description
      Previous value: -"Only these services."New value: +"Only these services: list of mite service ids, e.g. [42]. Default: all services."
    • 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."
    • changedInput schema / properties / user_id / description
      Previous value: -"Only these users (needs a key that may see other users)."New value: +"Only these users: list of mite user ids, e.g. [7]. Needs an API key that may see other users. Default: all users the key may see."
  2. First observedv1.0.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, but the description adds real value beyond them: it discloses the return shape (rows of month/project/hours/revenue plus total), that revenue is null without rates, that there is no paging, and that aggregation happens server-side. Only minor gaps remain, e.g. exact currency handling or empty-result behavior.

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?

Three dense sentences, front-loaded with what the tool does, then sibling routing, then return/behavior notes. Each clause carries information; nothing is redundant.

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?

Despite having no output schema, the description fully specifies the return rows and the null-revenue caveat, and it covers period defaults and read-only/no-paging behavior. An agent has everything needed to call and interpret the result.

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?

Schema description coverage is 100%, so all seven parameters (including date keywords, list filters, and the billable flag) are already documented in the schema. The description only echoes the default period and return semantics, adding marginal parameter-level detail beyond structured fields, so baseline 3 applies.

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?

States a specific verb+resource+scope: 'hours and revenue per project and month for a period,' with the key distinguishing trait (grouping done server-side so whole years work). It explicitly names the sibling tools it is not (mite_report for other groupings, mite_list_time_entries for single entries), so an agent can route without opening schemas.

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?

Gives explicit when-to-use-this vs alternatives: 'For other groupings or totals use `mite_report`; for single entries use `mite_list_time_entries`.' The condition selecting each tool is stated, leaving nothing to inference.

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