Skip to main content
Glama
WYRE-AI

gorelo-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gorelo_list_time_entries

Read-only

Lists logged time entries across all tickets and tasks, filtered by users, clients, tickets, tasks, invoices, locations, or time windows. Use it to review, audit, or report on tracked work.

Instructions

Lists logged time across every ticket and task, narrowed by any of the filters.

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from a previous page; omit for the first page. Only valid against the same filters that produced it.
taskIdsNotask ids; keeps only time entries logged against any of them.
userIdsNouser ids; keeps only time entries belonging to any of them.
pageSizeNoNumber of items per page. Clamped to 1–200 (default 50).
clientIdsNoclient ids; keeps only time entries billed to any of them.
ticketIdsNoticket ids; keeps only time entries logged against any of them.
invoiceIdsNoinvoice ids; keeps only time entries billed on any of them.
locationIdsNoclient location ids; keeps only time entries whose ticket sits at any of them.
createdSinceNoISO-8601 timestamp; keeps only time entries created at or after it.
startedSinceNoISO-8601 timestamp; keeps only time entries whose work started at or after it.
updatedSinceNoISO-8601 timestamp; keeps only time entries updated at or after it. An entry that has never been changed is excluded.
createdBeforeNoISO-8601 timestamp; keeps only time entries created strictly before it.
startedBeforeNoISO-8601 timestamp; keeps only time entries whose work started strictly before it.
updatedBeforeNoISO-8601 timestamp; keeps only time entries updated strictly before it. An entry that has never been changed is excluded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed19 schema fields changedv1.1.1
    • addedInput schema / properties / clientIds / description
      Added value: +"client ids; keeps only time entries billed to any of them."
    • changedInput schema / properties / clientIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / createdBefore / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only time entries created strictly before it."
    • changedInput schema / properties / createdSince / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only time entries created at or after it."
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque pagination cursor from a previous page; omit for the first page."New value: +"Opaque pagination cursor from a previous page; omit for the first page. Only valid against the same filters that produced it."
    • addedInput schema / properties / invoiceIds / description
      Added value: +"invoice ids; keeps only time entries billed on any of them."
    • changedInput schema / properties / invoiceIds / items / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / locationIds / description
      Added value: +"client location ids; keeps only time entries whose ticket sits at any of them."
    • changedInput schema / properties / locationIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / pageSize / description
      Previous value: -"Items per page, clamped 1-200 (default 50)."New value: +"Number of items per page. Clamped to 1–200 (default 50)."
    • changedInput schema / properties / pageSize / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / startedBefore / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only time entries whose work started strictly before it."
    • changedInput schema / properties / startedSince / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only time entries whose work started at or after it."
    • addedInput schema / properties / taskIds / description
      Added value: +"task ids; keeps only time entries logged against any of them."
    • addedInput schema / properties / ticketIds / description
      Added value: +"ticket ids; keeps only time entries logged against any of them."
    • changedInput schema / properties / updatedBefore / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only time entries updated strictly before it. An entry that has never been changed is excluded."
    • changedInput schema / properties / updatedSince / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only time entries updated at or after it. An entry that has never been changed is excluded."
    • addedInput schema / properties / userIds / description
      Added value: +"user ids; keeps only time entries belonging to any of them."
    • changedInput schema / properties / userIds / items / type
      Previous value: -"number"New value: +"integer"
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that results span "every ticket and task" (i.e. account-wide default scope), but says nothing about ordering, caps on returned results beyond the schema's pageSize, or permission scoping. With annotations present, this is a modest but real addition.

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

Conciseness4/5

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

A single front-loaded sentence with no filler; the verb and scope come first. It is arguably too terse for a 14-parameter tool, leaving room for one clarifying clause about filter combination.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter, unpaginated-by-default list tool with no output schema, the description should at least state result ordering, whether filters AND together, and what an unfiltered call returns. The schema carries the parameter detail, but these aggregate behaviors are left unstated.

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% across all 14 parameters, so the schema already explains cursors, page sizes, id arrays and ISO-8601 boundaries in detail. The description adds only the general notion that filters narrow the result set, without clarifying combination semantics or whether filter arrays are ORed internally.

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

Purpose4/5

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

States a specific verb and resource: "Lists logged time across every ticket and task," which distinguishes it from the sibling get/create/update time-entry tools. The scope phrase "across every ticket and task" signals a broad, unfiltered-by-default collection, though no sibling is named explicitly as an alternative.

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

Usage Guidelines3/5

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

"Narrowed by any of the filters" implies this is the query tool to reach for when you want a filtered set of time entries, but there is no explicit when-to-use/when-not guidance, no mention of how filters combine (AND vs OR), and no pointer to gorelo_get_time_entry for single-record retrieval.

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