Skip to main content
Glama
Stefan39

mite

by Stefan39
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List time entries

mite_list_time_entries
Read-only

List individual time entries for a date range, newest first, with optional filters for customer, project, service, user, billable, or locked status. Use it to find specific entries and their IDs.

Instructions

Lists single time entries from mite for a period, newest first, optionally filtered by customer, project, service, user, billable or locked. Use it to find individual entries or their ids; for totals use mite_report, for one known entry use mite_get_time_entry. Each row has hours, revenue in currency units (null if none), the locked flag and the note. Returns at most limit entries per page (default 100, max 1000) and has_more when further pages exist; the period defaults to 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).
pageNoPage number, starting at 1, e.g. 2. Default: 1.
limitNoEntries per page, 1–1000, e.g. 50. Default: 100.
lockedNotrue = only locked, false = only unlocked, e.g. false. Default: both.
user_idNoOnly these users: list of user ids, e.g. [7] (needs a key that may see other users). Default: all users the key may see.
billableNotrue = only billable, false = only non-billable, e.g. true. Default: both.
project_idNoOnly these projects: list of project ids, e.g. [789]. Default: all projects.
service_idNoOnly these services: list of service ids, e.g. [42]. Default: all services.
customer_idNoOnly these customers: list of customer ids, e.g. [123, 456]. Default: all customers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.0.1
    • changedInput schema / properties / billable / description
      Previous value: -"true = only billable, false = only non-billable."New value: +"true = only billable, false = only non-billable, e.g. true. Default: both."
    • changedInput schema / properties / customer_id / description
      Previous value: -"Only these customers."New value: +"Only these customers: list of 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 / limit / description
      Previous value: -"Entries per page (1–1000)."New value: +"Entries per page, 1–1000, e.g. 50. Default: 100."
    • changedInput schema / properties / locked / description
      Previous value: -"true = only locked, false = only unlocked."New value: +"true = only locked, false = only unlocked, e.g. false. Default: both."
    • changedInput schema / properties / page / description
      Previous value: -"Page number, starting at 1."New value: +"Page number, starting at 1, e.g. 2. Default: 1."
    • changedInput schema / properties / project_id / description
      Previous value: -"Only these projects."New value: +"Only these projects: list of 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 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 user ids, e.g. [7] (needs a key that may see other users). Default: all users the key may see."
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the read-only annotations, the description discloses ordering, returned row fields, revenue nullability, the locked flag, pagination behavior with `limit` and `has_more`, and the default reporting period. This is substantive behavioral context not present in the annotations.

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 description is dense but front-loaded: purpose and routing come first, then return shape and pagination details. Every sentence contributes either selection guidance or invocation-relevant behavior.

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?

With ten optional parameters and no output schema, the description supplies the missing return-shape and pagination information an agent needs. It also explains the period default, so the tool can be invoked correctly even with no arguments.

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 coverage is 100%, so all ten parameters are already documented, including the date keyword semantics and the `user_id` visibility caveat. The description summarizes filters and pagination defaults but adds little parameter meaning beyond the schema, making the baseline 3 appropriate.

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 states a specific verb and resource ('Lists single time entries'), the ordering ('newest first'), the filtering dimensions, and explicitly contrasts itself with `mite_report` and `mite_get_time_entry`. An agent can distinguish this from the reporting siblings without inspecting 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?

It gives explicit use cases ('find individual entries or their ids') and names the alternatives: totals should use `mite_report`, and a known single entry should use `mite_get_time_entry`. The routing decision between sibling tools is unambiguous.

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