solidtime-mcp

solidtime_time_entries_list

Read-only

Retrieve and filter Solidtime time entries by member, project, client, tag, task, date range, active or billable status, or type to review tracked work.

Instructions

List time entries. GET .../time-entries. Filter by member, project, client, tag, task, start, end, active, billable, type.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "solidtime_time_entries_list"
  }
}

Input Schema

Name	Required	Description
`end`	No	UTC timestamp like "2000-02-22T14:58:59Z".
`type`	No
`limit`	No
`start`	No	UTC timestamp like "2000-02-22T14:58:59Z".
`active`	No
`offset`	No
`tag_ids`	No
`billable`	No
`task_ids`	No
`member_id`	No
`client_ids`	No
`member_ids`	No
`project_ids`	No
`rounding_type`	No
`tag_match_type`	No
`only_full_dates`	No
`organization_id`	No	Organization UUID. Falls back to SOLIDTIME_ORGANIZATION_ID, then a single membership from GET /v1/users/me/memberships.
`rounding_minutes`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 5, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile needs no restating. The description adds the HTTP verb/path, which is modest context, but says nothing about pagination (limit/offset exist in the schema), default page size, ordering, or result volume for what could be a large listing.

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?

Two short sentences, front-loaded with the action and immediately followed by the filter surface; no filler. It is tight to the point of being terse, but nothing is wasted.

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

Completeness2/5

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

For an 18-parameter list tool with 17% schema coverage and no output schema, the description is far too thin. An agent still cannot tell whether filtering is AND-ed, whether date bounds are inclusive, how pagination terminates, or what shape the entries take, all of which are needed to call it correctly.

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

Parameters2/5

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

Schema description coverage is only 17% across 18 parameters, so the description must compensate and largely fails to. It names ten filter dimensions but leaves limit, offset, organization_id, rounding_type, rounding_minutes, tag_match_type, only_full_dates, and active/billable semantics unexplained; it also says "member" where the schema has both member_id (singular) and member_ids (array), creating ambiguity about which to use.

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?

"List time entries" gives a specific verb plus resource, and the endpoint hint (GET .../time-entries) removes ambiguity about what is returned. It does not distinguish itself from nearby siblings such as solidtime_time_entries_aggregate or solidtime_time_entries_export, which also read time-entry data.

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?

The list of filter dimensions implies the intended use (narrowing a set of entries), but there is no explicit when-to-use guidance versus time_entries_aggregate, time_entries_export, or time_entries_aggregate_export. No prerequisites, no exclusions, no mention of paging behavior.

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

Deploy Server